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
I expect the popup menu will hide (or show when its hidden) and not re-open again when clicking on the arrow button on any resource property in the inspector:
Steps to reproduce
Click on any resource/object property in the inspector
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered:
Confirmed in 3.x. Just to clarify as I initially misunderstood the GIF, on first click the PopupMenu is shown properly and doesn't flicker. The problem is that then clicking the arrow again makes it hide and reshow right away, instead of just hiding.
Chaosus
changed the title
Inspector resource menu re-opens instead of just hide after clicking on scrolling button
The Inspector resource selection menu re-opens instead of just hiding after clicking on the arrow button
Feb 8, 2022
The EditorResourcePicker::_update_menu() is called every time the arrow button is clicked. And this function calls edit_menu->popup();. I tried checking if edit_menu is visible and only if not - calling popup(). But I don't think its possible because it gets hidden before that (the hide() function gets called by some signal, so maybe it gets hidden automatically because of mouse click outside the edit_menu area?).
Also the OptionButton's arrow button (e.g. CanvasItem -> Texture -> Filter) instead of hiding if already visible on pressed, it opens again and then hides so it should probably get fixed too?
Godot version
3.x/4.0(be1adf4)
System information
Windows 10
Issue description
I expect the popup menu will hide (or show when its hidden) and not re-open again when clicking on the arrow button on any resource property in the inspector:
Steps to reproduce
Click on any resource/object property in the inspector
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered: