Closed lunabunn closed 3 years ago
Verified everything working as expected (in Chrome, version 87.0.4280.141). Chrome has a weird bug where if you have the developer console on, the cursor changes only take place when a mouse event is fired, but seems like a minor issue. Implementation still isn't thread-safe. Does wasm support threads now?
As a sidenote, Cursor::PointingHand => LoadCursorW(null_mut(), IDC_ARROW),
seems like a typo in the Windows implementation for set_cursor
. Should be IDC_HAND
.
Implementation still isn't thread-safe. Does wasm support threads now?
Browser callbacks always call into kapp
on the main thread and kapp's
Application
, EventLoop
and Window
are !Send
.
So even if some other Wasm parts run on other threads (in web workers) the kapp
code is thread safe as it's only interacting directly with the main thread.
Merged! Thanks for fixing up some of these missing parts. It's really appreciated! 👍
UNTESTED!
Fixes #5, fixes #6. Might be worth noting that the implementation is not thread-safe.