-
-
Notifications
You must be signed in to change notification settings - Fork 20k
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
[TRACKER] Moving arrays of properties edition to the Inspector. #52463
Comments
These are already array properties, so I don't think it applies here. |
Ah yeah that's true. Removing. |
i cant select the items in the itemlist, is it a known issue ? related to this ? or should i open a new issue ? |
GraphNode has slots property that could also use property array. The problem is that the slot count is constant and only depends on the node's children. Maybe property array could be improved to suport this case? EDIT: |
I want to be able to move the slots around - for example, if I add a new child to the node, and place it at the start, I would want to move the new slot to the start as well, to move the other slots alongside the old children. I believe that a generic array property control would allow for that? If it does, then I'll be really happy if GraphNode would get this treatment |
Godot version
master
Issue description
Since #52277 is implemented, we can now move several arrays of properties to this new system. This tracker aims to list all properties to either expose, move from a custom editor, or format as an array in the inspector. Basically, anythings that would benefit from the new property arrays implementation can go here.
So here is the list:
Potential includes to discuss:
...
Don't hesitate to comment anything you would like to be added here.
The text was updated successfully, but these errors were encountered: