-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Scenes are unable to remember it's nodes fold state #3395
Comments
Yes, this would be quite useful to have by default, especially as scenes get bigger. I don't think it should be too hard a task for the developers and would be a good fit for the upcoming usability release. |
I don't think this should be default, as it is counter-intuitive on small scenes. I would propose this to go into the settings. |
Could there be a threshold value that folds the tree or not based on the number of nodes that are inside it? You do have a point of this possibly being counter-intuitive for some scenes, but then you would have the far larger scenes people might have for game levels. |
Personally I assume it would be the best to just remember fold state between sessions, but if this is problematic I guess everyone will be pleased for an option in editor settings. |
Could another option be a keyboard shortcut to Collapse All (e.x.: Ctrl Shift +)/Expand All (e.x.: Ctrl Shift -)? |
at some point it did remember fold state.. maybe it broke? On Sat, Jan 23, 2016 at 8:56 AM, Ignacio Etcheverry <
|
Maybe it was in the scene metadata that were for the major part removed? There is still some (IMO) VCS-annoying metadata about whether the panel to open is 2D, 3D or Script. I think we should keep metadata as they are useful but make sure to save them in the user datadir (~/.godot) instead of hardcoding them in scene files. |
no, I think it was saved in the node metadata, just like bone information On Sat, Jan 23, 2016 at 10:26 AM, Rémi Verschelde notifications@github.com
|
Maybe another |
it works on scn but fails on tscn? On Sun, Jan 24, 2016 at 2:48 PM, eska014 notifications@github.com wrote:
|
Just tested and it remembers the folded state fine. Maybe 2493cb1 fixed it? |
no i don' t thinl that's related.. On Sun, Jan 24, 2016 at 3:56 PM, Ignacio Etcheverry <
|
Gave it a test with current master head, looks like it only happens for instanced scenes, independently of file type. Not sure if that is even unintended |
@eska014 looks like you are right, but I don't think it might be intended. |
This is a big productivity killer for me. If it is not fixed at least a collapse all button would be nice. |
@eska014 suggested this happens only for inherited scenes, well I can tell for sure that this is not a rule, I can tell for sure some bigger 'normal' scenes in my project are affected as well. |
Was testing this today, and will test more in next days. So far it works splendidly! |
Edit: from Eska tests it seems this bug is related to scene inheritance
Currently when we are opening new scene all the nodes in the tree in 'scene' tab are unfolded at the start. I think the scene should remember 'fold status' between sessions. Eventually all the nodes below first level should be folded by default.
Further more if we change scene and come back the tree always will be unfolded - despite the fact we have already folded it in mean time:
The text was updated successfully, but these errors were encountered: