| |
| |
|
| - Page 1 - |
|
ByteAttack | Hello Community,
i want gladly whom Click in a ListView evaluate.
though have I yet others inquire walk, sodas one WaitInput for my WhileNot Loop not question comes. I must everything with GetMessage make.
example:
the functions too lovely, still unfortunately scrolls then the ListView with my Cursor always with... the happens with WaitInput but not  |
|
| |
| |
| |
|
| |
| |
| - Page 2 - |
|
|
ByteAttack | I must GetMessages take, so the window again new aufgebaut becomes, if the size changes. the works of course too with Waitinput, but unfortunately not always, there sometimes at Change the Window hold no Waitinput for Profan stattfindet...
 |
|
| |
| |
| |
|
|
ByteAttack | my god, How unhöfflich. wished all thank, The me helped having.
Something like... |
|
| |
| |
| |
|
|
 | No then will need you no Getmessages. 
look you time in the Library in the area eleganteste Solution my Posting on.
there see You How tidy it too with Waitinput - and of course Live! - functions.
salvo.  |
|
| |
| |
| |
|
|
Frank
Abbing | Hi,
> by me scrolls The LV too wrong. your example working - it's located not on the Maustreiber
> - sooner on it the The messages not reset go. there wiederrum should Frank
> time look How it this with the XProfan-Getmessage arrange can.
Yes, by me exit the ungewollte Scrolling on.
> I must GetMessages take, so the window again new aufgebaut becomes, if itself
> the stature changes. the works of course too with Waitinput, but unfortunately not always, there
> sometimes at Change the Window hold no Waitinput for Profan stattfindet...
Have time whom Test made and the Subclassing to the first GetControlParas()-appeal with CloseMessages() abgestellt. and see there: the komische Scrolling is nevertheless there, though The List view.dll now in keinster point in that Messageshandling eingreift...
Have whom Error means not Subclassing sought, separate in GetControlParas(). thereby fell me The Message LVM_ENSUREVISIBLE on, The I use, circa Entries visible To make, The only semi in the list view To see are (if The User The time klicked has). Mach I The Message lane, is too the Error lane. The Message isn't absolutely necessary. I can tappt im dunkeln omit.
The problem is simply, the GetControlParas() with you in a Echtzeit-Loop called and is The Message now immediate anspringt, when the Mauszeige over so one entry hovers 
want You a Dll-Version without? |
|
| |
| |
| |
|
|
| |
| |
| |
| |
|
|
Jörg
Sellmeyer | [quote:92bc8dc0ae=Frank Abbing]Hi,
want You a Dll-Version without?[/quote:92bc8dc0ae]
[AUFSPRING_HUEPF]i will too a!![/AUFSPRING_HUEPF] |
|
| |
| Windows XP SP2 XProfan X4... und hier mal was ganz anderes als Profan ...  | 05/16/05 ▲ |
|
| |
|
|
ByteAttack | means if you The Messages  eh not for necessary hälst, throw tappt im dunkeln still generally from the ListView.dll out - or |
|
| |
| |
| |
|
|
| The Message has sure your Legitimacy - therefore my I Yes it would Perhaps meaningfully of Frank simply one second GetControlParas To invent.
or it building a Stopper - which to Getmessage laid would.
salvo. |
|
| |
| |
| |
|
|
Frank
Abbing | Hi,
The Message use I different to put in the Dll and generally is tappt im dunkeln very meaningfully and even unablässig. only on this place went it too without.
iFs Schalteridee find I but yet rather, therefore I will these time ex Version 1.7 install 
Marc-Gordon: I personally would always WaitInput with Timer use, instead of GetMessages. so I had yet never any Problems, what about me use it really often... |
|
| |
| |
| |
|
|
| Waitinput with Timer is still but sooner not recommendable - considerate one - the always The Messages geklaut go. whenever I NEN Timer einsetzte - then went z.B. the close only yet To 99% - almost independent of Timerwert. the Timernutzen find I is Real ne Notlösung. therefore have I Yes The Thread.Pcu written - there Gibts no Messageklauereien More - and one can so much time How one wants - too with very very small Timerwerten in the Echtzeitbereich.
salvo. |
|
| |
| |
| |
|
|
Frank
Abbing | Hi,
I have The announced function installed. in the next Version becomes tappt im dunkeln available stand:
ForbidScrollMessage(F)
Prevented the automatic Scrolling of only to that part visible Items.
F : Long - Flag
on some to put uses The List view.dll a Message, which only partly visible Entries complete into List view einschiebt.
the can but once in a while To unwanted shifts lead, namely always then, if in the Message-Loop not Waitinput using becomes. concerned hiervon are then The functions SelectLine(), GetControlParas() and GetOwnControlParas().
ForbidScrollMessage() is moreover virtual, the automatic Sichtscrolling short-term auszuschalten, if these functions in the program using and be The Message-Loop no WaitInput contain. short-term therefore, because the betroffene Message namely in Edit- and Drag&Drop mode using and is in the switched off status otherwise very unerwünschte effects produzieren becomes!
F=0 is the Normalzustand. is F=1, then is the Autoscrolling deaktiviert.
ForbidScrollMessage(1)
y&=Getcontrolparas(area#)
ForbidScrollMessage(0)
If y&<>0
...
> Waitinput with Timer is still but sooner not
> recommendable - considerate one - the always
> The Messages geklaut go. whenever
> I NEN Timer einsetzte - then went z.B.
> the close only yet To 99% - almost independent
> of Timerwert. the Timernutzen find I
> is Real ne Notlösung. therefore have I
> Yes The Thread.Pcu written - there
> Gibts no Messageklauereien More - and
> one can so much time How one wants - too
> with very very small Timerwerten in the Echtzeitbereich.
Threads are here but neither The Ideallösung, there tappt im dunkeln one Program still heavy brake. with one additional Thread has my Hauptprogramm only yet 50% Power. with two Threads quite only 33% etc.
my programs with Timern works anyhow less with Messages, and if, then use I The User Messages, The in each drop get by (see my SpriteRotator) or yet rather my Message.dll, The in the Subclassing stick and each yet so small Message registered. The Dll stops I personally for Ideallösung...  |
|
| |
| |
| |
|
|
| is of course offtopic - but with the Thread.Pcu behave it itself differently. I integrate Threads in Callbacks - set above another intelligente management - and these deals The Thread.Do. with gekonnter management inside the Thread.Do by the Programmer is the additional Processor load utterly beside the point - sozusagen hardly spürbar. The art bestand hold therein The Possibility To create - in XProfan Threadähnlich program to - with the benefit the everything inside the own Program happens - circa z.B. on any variables/Procedures zurückgreifen to. The Thread.Pcu is means sooner one very gelungener and fehlerfreier ambulation on Messers cut - and a pure Vorteilsmaschine. :/: 
salvo. |
|
| |
| |
| |
|
(456)
Deutsch
English
Français
Español
Italia