You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Monitors are currently being constantly iterated over in ImGui_ImplSDL3_NewFrame.
On macOS, SDL_GetDisplayUsableBounds shows to be about ~90% of the NewFrame cost, around 3% of my entire app.
I may be wrong, but I assume that this could be replaced by SDL's display events e.g. SDL_EVENT_DISPLAY_ADDED/SDL_EVENT_DISPLAY_REMOVED/SDL_EVENT_WINDOW_DISPLAY_SCALE_CHANGED
Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
No response
The text was updated successfully, but these errors were encountered:
Unfortunately there's no indicator on SDL front that work area may have changed so we started polling for this.
Will move this discussion to SDL3 repo, either the performance issue needs to be addressed either it would be good to have a signal for work area change.
Version/Branch of Dear ImGui:
docking/fonts
Back-ends:
SDL3 + SDL_GPU
Compiler, OS:
macOS Clang 16
Full config/build information:
No response
Details:
Monitors are currently being constantly iterated over in
ImGui_ImplSDL3_NewFrame
.On macOS,
SDL_GetDisplayUsableBounds
shows to be about ~90% of theNewFrame
cost, around 3% of my entire app.I may be wrong, but I assume that this could be replaced by SDL's display events e.g.
SDL_EVENT_DISPLAY_ADDED
/SDL_EVENT_DISPLAY_REMOVED
/SDL_EVENT_WINDOW_DISPLAY_SCALE_CHANGED
Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
No response
The text was updated successfully, but these errors were encountered: