You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To prevent unaccepted values I think it would be really nice if custom properties could support a datatype "Enumeration".
That way, when adding objects with the Scripting API, we could easily "protect" the user from adding unaccepted values by providing a list of values to choose from.
If this is not possible, I suggest adding a signal to be emitted when a objects custom_property value was changed. At least that way we could verify the value and show a hint to the user that the given value is not accepted
The text was updated successfully, but these errors were encountered:
This sounds like a duplicate of #1211, which was recently implemented and will be available in Tiled 1.8. I'm still working on making the custom enum (and class) types available in the scripting API, but the rest of the feature is available in the Tiled 1.8 beta.
To prevent unaccepted values I think it would be really nice if custom properties could support a datatype "Enumeration".
That way, when adding objects with the Scripting API, we could easily "protect" the user from adding unaccepted values by providing a list of values to choose from.
If this is not possible, I suggest adding a signal to be emitted when a objects custom_property value was changed. At least that way we could verify the value and show a hint to the user that the given value is not accepted
The text was updated successfully, but these errors were encountered: