gdevelop allows selecting instances on a hidden layer #669

[GDevelopGameCreator]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm not a developer or programmer, but I downloaded 3 days ago GDeveloper from an official website and it still have the same issue, that was resolved 5 years ago here. "Fix bug #661 - gdevelop allows selecting instances on a hidden layer #669". If it was fixed in the source code, I don't know how to compile that source code into a working program.

#661

Steps to reproduce

• Create 2 layers
• Put objects on both layers
• Hide one of the layer
• Select (mouse selection a zone) or just move the mouse around : hidden object react while it shouldn't

GDevelop platform

Desktop

GDevelop version

GDevelop-5-Setup-5.2.166.exe

Platform info

Windows 10

Additional context

No response

[AlexandreSi]

I cannot reproduce the bug you're describing. Would it be possible to record your screen while the bug is present?

[GDevelopGameCreator]

I did a recording of the issue. Thank you.

https://www.veed.io/view/320671de-eeb9-465e-a496-feceffb08cf8?sharingWidget=true&panel=share

[AlexandreSi]

Thanks for the recording!
I did not understand that you were talking about a bug in-game and not in the editor.
I think that this possibility of selecting hidden objects has always been there and could be considered as a feature.
We could add a parameter to the behaviour that would read "Prevent selection of object when hidden" and an action to tweak this parameter.
In the meantime, you can add an event with:

• Conditions:
  • Object is hidden
  • Trigger once
• Action:
  • Activate behaviour "Draggable": no

(and the other way around to activate it when the object is not hidden)

[Silver-Streak]

I can confirm: Visibility of an object has never had any impact for any other events unless you are using the "object is hidden/visible" condition in your event.

This has always been true, and is unrelated to the issue mentioned, which was for objects being selected in the IDE when the layer was hidden (#669)

Alexandre's recommend solution is the right way to go about this logic wise, and I don't know that you would want to change the engine to behave differently.