Joe Wilm f3db0ba641 Fix x11 interrupt to actually wake event loop ...

This is the same behavior as with WindowProxy::wakeup_event_loop in
previous versions.

Unfortunately, `EventsLoop::interrupt` is also the recommend way to exit
a `run_forever` loop from within the event handler callback. Pushing an
extra event on the queue in that case is simply wasteful. Changing this
would require a refactor taking one of two possible forms:

1. Add a method *in addition* to interrupt intended for waking up the
   event loop
2. Add a return type to the event callback like

    enum Continue { True, False }

   which would be used in lieu of the atomic interrupt flag.

2017-05-09 09:51:00 -07:00

..

os

Readd pub import erroneously removed

2017-03-15 10:11:43 +01:00

platform

Fix x11 interrupt to actually wake event loop

2017-05-09 09:51:00 -07:00

api_transition.rs

Richer input events

2017-04-23 01:08:15 -07:00

events.rs

Merge pull request #164 from Ralith/rich-input

2017-05-07 08:35:03 +02:00

lib.rs

Richer input events

2017-04-23 01:08:15 -07:00

window.rs

Update the macOS backend to the new futures-compatible API.

2017-02-03 23:05:57 +11:00