945babc619
In some cases it can happen, that the order of input events and window events is not followed, when input buffering or input accumulation is active. The display server order `InputEvent` => window-event gets changed to window-event => `InputEvent` which becomes problematic in certain situations. This PR makes sure, that the order is adhered to by flushing input events before a window event is sent. Previously this problem was mitigated by discarding these delayed events. But this solution was problematic in the setting of android input events. |
||
|---|---|---|
| .. | ||
| 2d | ||
| 3d | ||
| animation | ||
| audio | ||
| debugger | ||
| gui | ||
| main | ||
| resources | ||
| theme | ||
| property_list_helper.cpp | ||
| property_list_helper.h | ||
| property_utils.cpp | ||
| property_utils.h | ||
| register_scene_types.cpp | ||
| register_scene_types.h | ||
| scene_string_names.cpp | ||
| scene_string_names.h | ||
| SCsub | ||