-
-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
imgui UI out of bounds in example "imgui-winit" #338
Comments
It looks like an off by one based on the error message, but this is a new failure mode to me. Do your displays have different logical pixel sizes? Maybe that has something to do with it. I honestly have not done a lot of testing with multiple displays and handling changes to the scaling factor. I can put together a setup and try to reproduce this. Because that example uses the scaling factor within its resize handler, I suspect these two events need to be handled simultaneously. That's my current theory. |
thanks @parasyte . My setup is basically a laptop that i connect to 2 different monitors (1920x1080 and 1920x1200) throughout the day (not at the same time). ill have a look tomorrow and will try to come up with a solution, thanks for the advice and for the great project, ive found it very useful :)) |
I just cloned the repo and ran through some examples and hit this. My message was a bit different though:
This is on an iMac 5K (x86) running the latest OS and run: 15.1 and Rust rustc 1.82.0 (f6e511eec 2024-10-15). |
The (truncated) backtrace:
|
Clarification: this is a plain vanilla iMac setup and no second monitor. I don't think there's anything unusual about my setup. |
This is indicative of the window being hidden. Which should not cause a draw. (I would consider it a bug to redraw while the window is hidden. But I don't remember ever making a conscious decision to avoid redraws on hidden windows. It was identified in #174, though.) Also, see this discussion: #400. |
Whenever I switch between my monitors and run my program I get an instant crash before the first render. I narrowed it down to the UI drawing to a slightly bigger frame. I tried to recreate it in the example mentioned in the title and I also got the same error. A restart of my PC fixes it sometimes.
I tried tweaking the code, but I couldn't find a solution. Any advice?
The text was updated successfully, but these errors were encountered: