In making changes to sq.h I discovered that I had made a change for the scroll mouse logic which impacts some changes we want to make for multiple windows, but I not sure anyone is using this feature.
On os-x if you are using a wheel mouse I generate a mouse move event and pass up the axis direction and number of movements in the reserved fields, followed by the key-down/key char/key-up events for each simulated arrow key.
I believe other platforms just provide the key stroke data and do not pass up the raw wheel mouse data. As mentioned earlier this data is provided in the two reserved (undocumented) fields of the mouse event from EventSensor.
In looking at what is happening in the image, I can't see anyone actually using this data at this time.
Because of changes we're making I'm going to be dropping this information, since it's not duplicated on other platforms, this is an easier choice than adding another field to the event logic to support the windowIndex information.
If anyone has issues please let me know.
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
We are using this for Croquet, but we are happy to have it simply emit up-arrow and down-arrow keys for now, which I believe is the behavior on the Mac and Win. Regards,
David
On Jul 29, 2004, at 2:50 AM, John M McIntosh wrote:
In making changes to sq.h I discovered that I had made a change for the scroll mouse logic which impacts some changes we want to make for multiple windows, but I not sure anyone is using this feature.
On os-x if you are using a wheel mouse I generate a mouse move event and pass up the axis direction and number of movements in the reserved fields, followed by the key-down/key char/key-up events for each simulated arrow key.
I believe other platforms just provide the key stroke data and do not pass up the raw wheel mouse data. As mentioned earlier this data is provided in the two reserved (undocumented) fields of the mouse event from EventSensor.
In looking at what is happening in the image, I can't see anyone actually using this data at this time.
Because of changes we're making I'm going to be dropping this information, since it's not duplicated on other platforms, this is an easier choice than adding another field to the event logic to support the windowIndex information.
If anyone has issues please let me know.
--
==== John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================= ====
squeak-dev@lists.squeakfoundation.org