Re: user32: Don't try to move mouse to (-1,0).
On 2/6/11 5:33 AM, Vitaliy Margolen wrote: On 02/05/2011 07:10 AM, Jacek Caban wrote: This trigers screen edge action on KDE, which is 'Present Windows' in default configuration. mouse_event() generates relative mouse movement events unless MOUSEEVENTF_ABSOLUTE is specified. If you don't want a pointer to get near the edge then you should use SetCursorPos() instead. It's enough that we don't try to move the cursor up nor left when it's in the edge. Jacek
Re: user32: Don't try to move mouse to (-1,0).
On 02/05/2011 07:10 AM, Jacek Caban wrote: This trigers screen edge action on KDE, which is 'Present Windows' in default configuration. mouse_event() generates relative mouse movement events unless MOUSEEVENTF_ABSOLUTE is specified. If you don't want a pointer to get near the edge then you should use SetCursorPos() instead. Vitaliy.
Re: user32: Don't try to move mouse to (-1,0).
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=8925 Your paranoid android. === W7PROX64 (64 bit msg) === Timeout
