Btw, what about altering VM to generate a true mouse scroll events, so it wont be dependent from keyboard events anymore?
2009/11/18 Igor Stasenko siguctua@gmail.com:
2009/11/18 Andreas Raab andreas.raab@gmx.de:
Igor Stasenko wrote:
It does not fixes the problem for me :( I wonder, why mouse scroll behavior depends on flaps or locale..
Most likely because scroll events are delivered as Ctrl-UpArrow and Ctrl-DownArrow events and there is a chance that the input converters muck with that. I had a quick look but I couldn't find much. Some things you could try is:
- see if typing Ctrl-UpArrow and Ctrl-DownArrow scrolls text
works fine.
- check what running "Sensor kbdTest" shows when you operate the scroll
wheel
shows 30 16 31 16 in display corner, when i scrolling da wheel
- check the keyboard converter in World primaryHand to ensure it's correct.
it points to an UTF32JPInputInterpreter, which is wrong..
I found how to revert back to EN locale: Locale currentPlatform: (Locale isoLanguage: 'en')
after that, mouse scroll starts working again.
But back to the question: - why it not works in japanese locale? Is japanese guys not using mouse scroll, or their goverment prohibits from use a mouse scroll wheel? ;)
Cheers, - Andreas
-- Best regards, Igor Stasenko AKA sig.
On 18.11.2009, at 09:15, Igor Stasenko wrote:
Btw, what about altering VM to generate a true mouse scroll events, so it wont be dependent from keyboard events anymore?
+1
- Bert -
Where do you stop with that? The Mac (and some windows mice+drivers) lets you scroll in 360 degrees.
Just saying:)
On Wed, Nov 18, 2009 at 2:06 AM, Bert Freudenberg bert@freudenbergs.de wrote:
On 18.11.2009, at 09:15, Igor Stasenko wrote:
Btw, what about altering VM to generate a true mouse scroll events, so it wont be dependent from keyboard events anymore?
+1
- Bert -
2009/11/18 Ronald Spengler ron.spengler@gmail.com:
Where do you stop with that? The Mac (and some windows mice+drivers) lets you scroll in 360 degrees.
Oh... don't let me starting on this :) I think that Squeak should transparently allow interacting with all HIDs available on market: touchscreen, mices , voice control , joystick etc etc ;)
But to be serious.. a first mouse with scrolling wheel appeared long ago (in scale of computer's evolution). And most OS-es and GUIs have standartized these input events during last decade. And frankly, i don't see a reason, why Squeak VM still using workarounds for delivering these events to image side.
Just saying:)
On Wed, Nov 18, 2009 at 2:06 AM, Bert Freudenberg bert@freudenbergs.de wrote:
On 18.11.2009, at 09:15, Igor Stasenko wrote:
Btw, what about altering VM to generate a true mouse scroll events, so it wont be dependent from keyboard events anymore?
+1
- Bert -
-- Ron
On 2009-11-18, at 9:09 AM, Igor Stasenko wrote:
2009/11/18 Ronald Spengler ron.spengler@gmail.com:
Where do you stop with that? The Mac (and some windows mice+drivers) lets you scroll in 360 degrees.
Oh... don't let me starting on this :) I think that Squeak should transparently allow interacting with all HIDs available on market: touchscreen, mices , voice control , joystick etc etc ;)
But to be serious.. a first mouse with scrolling wheel appeared long ago (in scale of computer's evolution). And most OS-es and GUIs have standartized these input events during last decade. And frankly, i don't see a reason, why Squeak VM still using workarounds for delivering these events to image side.
For the iPhone VM I created a complex event type which passes up a smalltalk object. In this case a translation of the iPhone touch events to a smalltalk object. I could have passed up a bytearray and let EventSensor deal with it.
Maybe we need a raw mode where data is passed up in a bytearray then EventSensor is reponsible for assembling the data into a meaningful pattern.
-- =========================================================================== John M. McIntosh johnmci@smalltalkconsulting.com Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
Igor Stasenko wrote:
And frankly, i don't see a reason, why Squeak VM still using workarounds for delivering these events to image side.
Because they work. This was a very elegant hack which solved two problems: Bringing in the events at all, and making use of them immediately (since as up/down array all the editors know what to do with it). It'll be quite a bit more work to put the plumbing into place which delivers scroll events throughout all the UI environments that are in use. Doable, but work nonetheless.
Cheers, - Andreas
vm-dev@lists.squeakfoundation.org