Le 11/5/15 02:34, Sean P. DeNigris a écrit :

> Matthieu Lacaton wrote
>
>> Let's say for example thant I want to create a rectangle on the screen and
>> be able to move it up and down by pressing CTRL + up / down arrow and be
>> able to rotate it with the mouse wheel. Does this mean that on Linux I
>> just
>> can't
>>
>
 Mathieu contact Merwan to see if he has support for that.


With OSWindow events (based on SDL ones) I was able to do so without
trouble.
I was just surprised by VM events but no big deal.

2015-05-11 21:32 GMT+02:00 stepharo <steph...@free.fr>:

> Sean
>
> We are working on SDL based events so we should probably synchronise.
> Because mouse wheel should be an event and not simulated.
> Merwan is producing touch event.
> Stef
>
> Le 11/5/15 02:34, Sean P. DeNigris a écrit :
>
>> Matthieu Lacaton wrote
>>
>>> Let's say for example thant I want to create a rectangle on the screen
>>> and
>>> be able to move it up and down by pressing CTRL + up / down arrow and be
>>> able to rotate it with the mouse wheel. Does this mean that on Linux I
>>> just
>>> can't ?
>>>
>> Mathieu contact Merwan to see if he has support for that.
>
>
>  That is correct by default, but you can always hack the VM if you
>> reeeeally
>> want that behavior. Also, if you just wait a bit, I'm in the process of
>> remapping the wheel simulation shortcuts to be extremely less likely to
>> conflict with actual keyboard events. It is already done for Mac. I wrote
>> the patch for GNU/Linux & Windows, but didn't have machines available
>> when I
>> was testing (the code may take a bit of massaging to compile). The upside
>> is
>> that it's a backward compatible VM change, so you will be able to take
>> advantage of it in any Pharo version that will run on the latest VMs.
>>
>>
>> Matthieu Lacaton wrote
>>
>>> And does this mean that if I create an application able to react to mouse
>>> wheel, I need to code it differently for Windows and for Linux ?
>>>
>> No, you would code it the same way. In the image, MouseWheelEvents are
>> created regardless of the keyboard event used to simulate them. The only
>> thing different would be the keyboard equivalents.
>>
>>
>>
>
>

Reply via email to