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

Unclear documentation on Custom Resource Type #10612

Open
a2937 opened this issue Feb 4, 2025 · 5 comments
Open

Unclear documentation on Custom Resource Type #10612

a2937 opened this issue Feb 4, 2025 · 5 comments
Labels
area:manual Issues and PRs related to the Manual/Tutorials section of the documentation enhancement

Comments

@a2937
Copy link
Contributor

a2937 commented Feb 4, 2025

Your Godot version: 4.2

Issue description: On the custom resource sections, custom editors and data visualization is mentioned. But I don't think they current documentation covers how to make editors for custom types. As someone that thinks they might want an editable data table, additional documentation will help.

URL to the documentation page (if already existing): https://docs.godotengine.org/en/stable/tutorials/scripting/resources.html

@AThousandShips
Copy link
Member

@AThousandShips AThousandShips added area:manual Issues and PRs related to the Manual/Tutorials section of the documentation enhancement labels Feb 4, 2025
@a2937
Copy link
Contributor Author

a2937 commented Feb 4, 2025

Something similar.

@AThousandShips
Copy link
Member

Please detail what would be added to this new documentation that isn't in that tutorial

@a2937
Copy link
Contributor Author

a2937 commented Feb 4, 2025

In the Inspector plugin page, I would like to limit the kind of objects my editor is compatible with. I'd love to use an array of objects too, but I'm not sure how viable that is. I think additional documentation on the inspector plugin dealing with arrays could help.

@AThousandShips
Copy link
Member

The kind of input the inspector can edit is configurable, and would be good to add that to the tutorial, it should be possible using the _parse_property virtual function

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:manual Issues and PRs related to the Manual/Tutorials section of the documentation enhancement
Projects
None yet
Development

No branches or pull requests

2 participants