Thanks, Tim - what's odd is that windows only does this sometimes, not all the time.
Since the workaround is trivial, it's not a big deal, but I wanted to mention it in case it was a bug. On Dec 13, 2014, at 1:37 PM, Tim Jones <tolis...@me.com> wrote: > On Dec 13, 2014, at 1:43 PM, Christian Schmitz > <supp...@monkeybreadsoftware.de> wrote: > >> For some things it may make sense, as e.g. Mac OS 9 used to send mouse >> events regularly just to inform your app and let it continue a cursor >> animation. > > It’s the same for Windows newer SDKs as Windows supports animated mouse > cursors. > > Michael’s solution is pretty much what MSDN comments say to do for native > Windows development - paraphrasing a series of longer posts - > > If your application does not utilize animated cursors (game pointers, > decision pointers, busy pointers, etc.), simply ignore the duplicated > WM_MOUSEMOVE events until the window-relative X or Y coordinates reported are > different. > > Tim > > _______________________________________________ > Mbsplugins_monkeybreadsoftware.info mailing list > mbsplugins@monkeybreadsoftware.info > https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list mbsplugins@monkeybreadsoftware.info https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
