Scripting API - TiledObject - Allow for invisible / readonly custom properties
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
When placing a Object on an Object layer it gets an ID and Template assigned. Both are readonly.
I think it would be great if custom properties could either be invisible (not prefered) or be marked as readonly upon creation (prefered).
The use-case for this is that I am developing tools that create objects. I would like to assign the current extension version to the created object so I can later track down deprecated/old objects that need an update when my extension changed. Having a editable custom property (which is what I have right now) is pretty error prone
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how TiledObject custom properties are created and exposed through the scripting API. Compare the existing readonly behavior of object IDs and templates with the requested custom-property behavior. Done means tools can mark a custom property readonly when creating an object, preventing accidental edits while retaining its value for later version tracking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100