Skip to content
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

("Sticky"?) dropdown menu focus causes erratic mouse (de)select behaviour in editor collision layers (DisplayServer regression) #61773

Closed
ModularNucleus opened this issue Jun 7, 2022 · 6 comments

Comments

@ModularNucleus
Copy link

ModularNucleus commented Jun 7, 2022

Godot version

Godot alpha 4 - alpha 9

System information

Windows 10, Nvidia RTX3060 Ti, Vulkan Clustered

Issue description

I have tried to do a search, but have not found a report that seems to describe exactly the same issue, although #61758 may be related.

It seems that when using a dropdown menu, the focus can become stuck to the dropdown menu and affect subsequent mouse (de)select behaviour - e.g., in collision layer (de)selection.

Note: I have only tested the editor collision layer behaviour, not the actual collision layer behaviour. I assume this is an editor issue.

Video1 below:
With an Aread3D and a CollisionShape3D node - but not yet an actual collision shape - added to the scene, the collision layer (de)selection works as expected. However, after adding the collision shape via the shape dropdown menu, collision layer (de)selection becomes erratic. The issue might affect other editor items as well, but I haven't really checked.

Note: the dropdown menus are not displayed in the videos due to my screen capture software.

Godot.Alpha.9.-.editor.de.select.issue.-.edit.mp4

Video2 below:
After reloading the project, the (de)selection again works as expected. However, using the CollisionObject3D "disable" dropdown menu reintroduces the erratic behaviour.

Godot.Alpha.9.-.editor.de.select.issue.-.reloaded.project.-.edit.mp4

I can reproduce this issue in alphas 4-9, but not in alpha 3 nor earlier alphas. The issue thus seems to have been introduced in alpha 4.

Steps to reproduce

Open the included MRP:

  • Change the Area3D's collision layers. Observe that they behave as expected.
  • Use the "disable" dropdown menu (e.g., change / change and reset) above the collision layers. Observe that the erratic (de)select behaviour is introduced to the collision layer (de)selection.

Minimal reproduction project

Default.zip

@ModularNucleus ModularNucleus changed the title [Alpha 4 - Alpha 9] editor. ("sticky"?) dropdown menu focus causes erratic mouse (de)select behaviour in editor collision layers. [Alpha 4 - alpha 9 editor]. ("Sticky"?) dropdown menu focus causes erratic mouse (de)select behaviour in editor collision layers. Jun 7, 2022
@ModularNucleus
Copy link
Author

When the issue is present, (de)selection of the collision layer still works correctly through the collision layer dropdown menus. It seems it only affects the main fields.

@Calinou Calinou added this to the 4.0 milestone Jun 7, 2022
@Calinou Calinou changed the title [Alpha 4 - alpha 9 editor]. ("Sticky"?) dropdown menu focus causes erratic mouse (de)select behaviour in editor collision layers. ("Sticky"?) dropdown menu focus causes erratic mouse (de)select behaviour in editor collision layers (DisplayServer regression) Jun 7, 2022
@Calinou
Copy link
Member

Calinou commented Jun 7, 2022

Can you reproduce this after enabling Single Window Mode in the Editor Settings then restarting the editor?

@KoBeWi
Copy link
Member

KoBeWi commented Jun 8, 2022

Can't reproduce on Windows 10.
Does it always happen? Might be the same issue as #58609

@KoBeWi KoBeWi moved this to To Assess in 4.x Priority Issues Jun 8, 2022
@ModularNucleus
Copy link
Author

@Calinou No, I cannot reproduce this with "Single window mode" enabled. Without it, however, the issue is consistent.

@ModularNucleus
Copy link
Author

@KoBeWi Yes, it does always happen when not in "Single Window Mode", but it is fixable by Alt+tabbing, as in the issue you linked, until I use the dropdown menu - then the issue reappears.

@KoBeWi
Copy link
Member

KoBeWi commented Jun 10, 2022

Oooh this is interesting. I can reproduce it reliably and it has all of the symptoms from #58609. I'll close it as duplicate, but this is important finding.

@KoBeWi KoBeWi closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2022
Repository owner moved this from To Assess to Done in 4.x Priority Issues Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants