On Wed, Jul 29, 2009 at 4:48 PM, Darin Fisher <[email protected]> wrote:
> The solution: Instead of calling GetCursorPos you should either refactor > your code to be able to access input from mouse events consistently, or if > that is not feasible then call > GetMessagePos<http://msdn.microsoft.com/en-us/library/ms644938(VS.85).aspx> > instead > of GetCursorPos. That method returns the mouse position that was last > observed by the event loop. > Note: In occasional circumstances, GetCursorPos() is still correct. However, these are rare. You'd use this if, for example, you want to stick a fake mouse move event (that doesn't actually move the mouse) on the end of the event queue. Using GetCursorPos() ensures that your fake event won't actually move the mouse. If in doubt, you almost certainly want GetMessagePos(). By by unwanted detached tabs, > Darin needs a context-sensitive spellchecker :) PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
