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

Add autocompletion for animation, effect and point in behavior properties #5996

Open
D8H opened this issue Dec 3, 2023 · 1 comment
Open
Labels
✨ enhancement 👌good first issue Good issue if you want to start contributing to GDevelop 😤Non optimal UI A bug/issue where the UI is usable but not optimal

Comments

@D8H
Copy link
Collaborator

D8H commented Dec 3, 2023

Description

There are autocompletions in action and condition parameters that don't exist for behavior properties.

Solution suggested

Some insights:

  • Property types are chosen with a drop down list in EventsBasedBehaviorPropertiesEditor
  • Property fields are build by PropertiesMapToSchema
  • Fields used for parameters handle autocompletion: ObjectAnimationNameField, ObjectEffectNameField, ObjectEffectParameterNameField, ObjectPointNameField
  • Property types are mapped to primitive types in ValueTypeMetadata::ConvertPropertyTypeToValueType

Tests

It can be tested on this extensions

Manually check that generated functions use the right parameter type.
image

@D8H D8H added ✨ enhancement 👌good first issue Good issue if you want to start contributing to GDevelop 😤Non optimal UI A bug/issue where the UI is usable but not optimal labels Dec 3, 2023
@D8H
Copy link
Collaborator Author

D8H commented Feb 2, 2025

Done for animations in:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ enhancement 👌good first issue Good issue if you want to start contributing to GDevelop 😤Non optimal UI A bug/issue where the UI is usable but not optimal
Projects
None yet
Development

No branches or pull requests

1 participant