Hi Stef,

cool, looking forward to seeing it works :) Because we really need shift event

Cheers,
Alex

On Fri, Nov 21, 2014 at 11:13 PM, stepharo <stepharo@free.fr> wrote:
Hi alex

the way these low level events are managed sucks. This is why we started to reify them. Now with OSWindow (we should review the code)
and I hope it will get better. Also the VM was not generating event for shift and I hope that OSwindow will support that :)
Le 21/11/14 17:36, Aliaksei Syrel a ��crit��:
Hi Ben,

If at the end of InputEventFetcher>>waitForInput
you put "Transcript crShow: Time now"
and I think you'll be looking at as raw an event aas you can get.

Now this exhibits some strange behaviour?�� Pushing <shift> on its own does not produce an event, however pushing <shift> fast multiple times does generate events. ???
It's maybe because you move mouse, or randomly touch touchpad.

After some investigations and digging lower and lower till primitive methods, I realized that VM itself doesn't queue an event after user presses Shift. It's just a modifier bit, that is applied on a real events, such as mouse moves or normal keyboard events.

Cheers,
Alex
��