Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BUG in ListBox, mousemove fire ProgrammaticChange
Message
From
18/02/2004 09:23:31
 
 
To
18/02/2004 08:44:36
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00878222
Message ID:
00878270
Views:
11
Hi Fabio. I agree with you, but at the same time, I have to wonder how things all should tie together. Some events need to fire, even if you started the click on _Screen. You need to acknowledge the mouseenter, mouseleave, mousemove, drag events etc. If you drag something over to the listbox and drop it, should the change event then fire? There is a lot of stuff going on, and I'm not sure how the programmer should handle it all so that it's always consistent with what each developer might expect to have happen.

At the same time, though, I do agree that if any event needs to fire in this case, it should be the InteractiveChange event, not the ProgrammaticChange.

Overall, I'm not sure this is really a simple "black and white" issue. Lots of grey, I think.

>Alan,
>
>it is admirable the search for a justification of the VFP tantrums.
>
>VFP is a 99% stateless enviroment ( like a combinatorial machine ),
>it process Windows event messages.
>
>On this case,
>VFP do a banal task:
>it process Windows Mousemove events with Mouse left button down,
>and for any event with changing of items graphics area it
>exec ProgrammaticChange binded tokens.
>
>Try:
>- hold down left mouse button on Form, not on listBox
>- move the mouse on Listbox, ProgrammatiChange occurs !
>
>
>Strong proof:
>Now, leave form with listbox.
>- hold down left mouse button on _SCREEN area, not on listbox form
>- move the mouse on Listbox, ProgrammatiChange occurs !, and the form donnot have the focus !
>

>
>Exists a Web site with "programming staff rating" on internet ?
>
>Fabio
Previous
Reply
Map
View

Click here to load this message in the networking platform