Details
-
Task
-
Resolution: Done
-
P1: Critical
-
None
-
WinRT
-
-
2eda13c965497e41bb2d031f7890979a819d6438 9b19a69c89c07b02ab631c1ccfd4d89013b6ec45 7f41e56ec3e69569b62e9ee76537a1123fc66bfc
Description
The current eventdispatcher does nothing but call native ProcessEvents, sendPostedEvents and Window system events in an endless loop. That causes all applications to use one core to its fullest.
On desktop windows we use ProcessEvents in conjunction with a custom event to be send, so that WaitForMultipleObjectsEx returns in case we want explicitly the dispatcher to run.
StopProcessEvents could be used from some other thread maybe? But definitly we need to get a better solution.