-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Ui::with_layer_id
panics when given LayerId
is different from the Ui
's current one.
#5178
Comments
@Adanos020 Have you found any workarounds? I have a number of places I'm using |
@shadowbrok3r Unfortunately not. I'm hoping this will get resolved soon, as it breaks egui_dock and I can't release 0.14 in this state. |
@Adanos020 Ah I didn't realize I was talking to the creator of egui_dock, the code with |
@shadowbrok3r That would be grand, thanks. To be fair the whole egui_dock needs a rewrite, as it's becoming harder and harder to maintain it the more it grows. One thing I'm considering is replacing our drag-n-drop system with the dedicated |
Note: I ran the above example on Windows 10 (glow, wgpu) without any problems. |
Interesting, I'm having the issue in both Wasm and Arch Linux |
I'm also on Arch Linux. |
Note that this is a |
The problem was introduced in |
Describe the bug
Title says it all. This renders the function utterly useless.
To Reproduce
Simply run this code and observe it panic straight away. The only dependency here is eframe 0.29.0. The issue still persists on
master
at the time of writing.Callstack:
Expected behavior
The application should not panic, and the new
Ui
should have the givenLayerId
as intended.The text was updated successfully, but these errors were encountered: