Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trapping Mouse Clicks
Message
From
04/01/2010 07:34:38
 
 
To
02/01/2010 12:21:09
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 7 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01441595
Message ID:
01441882
Views:
39
>>My app has a logging function. I put some log code in the MouseDown event and it never gets executed through the entire sequence. I did the same on the other events; they execute, but don't return any useful value. I have not yet tried MouseUp. I'm not optimistic, but it's worth a try I guess.
>
>I didn't mean your own logging (though it should at least show that code was run - and nMouse should have a value), I meant SET EVENTTRACKING to a file and then looking at what happens and in what sequence. I've often found that things there don't happen in an order I would expect. It's a magnifying glass... though if something isn't there, it won't find it.

Just an FYI, Dragan: your surmise on MouseUp turns out to be correct; the MouseUp nButton parameter does return 1 for left click and 2 for right click in my scenario. I had come up with a work-around before I discovered this, so it's sort of a moot point now, but good to know for future reference. [Added later] And I just discovered that MouseUp fires AFTER GotFocus, so it does no good in my scenario in any case. Rats.
Ray Roper
Previous
Reply
Map
View

Click here to load this message in the networking platform