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

[TRACKER] Moving arrays of properties edition to the Inspector. #52463

Open
3 of 9 tasks
groud opened this issue Sep 7, 2021 · 5 comments
Open
3 of 9 tasks

[TRACKER] Moving arrays of properties edition to the Inspector. #52463

groud opened this issue Sep 7, 2021 · 5 comments

Comments

@groud
Copy link
Member

groud commented Sep 7, 2021

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:

  • AnimationPlayer
  • SpriteFrames animations
  • Gradients points
  • LayeredTexture
    ...

Don't hesitate to comment anything you would like to be added here.

@groud groud added this to the 4.0 milestone Sep 7, 2021
@KoBeWi
Copy link
Member

KoBeWi commented Sep 7, 2021

Line2D, Line3D, CollisionPolygon2D, Path2D, Path3D, Polygon2D, NavigationPolygon, CurveTexture, CurveXYZTexture

These are already array properties, so I don't think it applies here.

@groud
Copy link
Member Author

groud commented Sep 7, 2021

These are already array properties, so I don't think it applies here.

Ah yeah that's true. Removing.

@barbaros83
Copy link

barbaros83 commented Dec 5, 2021

i cant select the items in the itemlist, is it a known issue ? related to this ? or should i open a new issue ?

@KoBeWi
Copy link
Member

KoBeWi commented Jan 10, 2022

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:
It's already implemented when you use the READONLY flag.

@KoBeWi KoBeWi removed this from the 4.0 milestone May 1, 2022
@guyguy2001
Copy link

GraphNode has slots property that could also use property array. ...

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

5 participants