|
From: Arjen M. <Arj...@de...> - 2018-07-02 07:30:47
|
Hi everyone, > -----Original Message----- > From: Donal K. Fellows [mailto:don...@ma...] > > If we mapped that also onto <MouseWheel>, but with the detail (%d) field different > (it's currently not defined for that event type). That'd allow us to keep %D for the > size of the scrolling action, which is something we should definitely retain (since > some mouse drivers do funky stuff with scrolling when you click the wheel). We, of > course, have complete control over how the detail field is rendered in this case. > > At a low level in the guts of tkBind.c, we currently pretend that a MouseWheelEvent > (itself entirely internal to Tk) is somewhat like a KeyEvent. Except with a bunch of > fields missing a lot of the time... > That is indeed how I have defined a MouseWheelEvent for Linux in my local repository. I had not thought of the detail field. As for existing applications: they will currently handle mouse wheel events in a platform-specific way. If they want to take advantage of the intended uniform way, the bindings will have to change, no matter what. Of course, it is preferrable if the old way is still possible. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |