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

An easier way to use ResourceCollection #102

Open
auralluring opened this issue Apr 20, 2022 · 0 comments
Open

An easier way to use ResourceCollection #102

auralluring opened this issue Apr 20, 2022 · 0 comments

Comments

@auralluring
Copy link

Right now ResourceCollection requires you to set a script for the base type. This makes for some UI that is sort of clunky and hard to figure out. (at least for me) But I discovered something recently with EditorResourcePicker. Basically, it has a base_type property which takes a name string of the base type and filters the list down to that class and its inheritors. You might assume this doesn't include custom resources (as is the case for nearly everything else in the engine that uses class names as strings), but it does!

This would allow us to include engine classes as well as an overall more intuitive UI. It would, of course, require the user to register their class, but I think that's a reasonable ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant