Import tileset as .tsx - not only create tileset as now
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
**Is your feature request related to a problem? Please describe.**
Right now user have create tileset and then save as .tsx.
Looks that this is basic problem is in case is no option to import .tsx but create new and save/override exit this same if user want use this same tile set.
**Describe the solution you'd like**
Import like Export.
**Describe alternatives you've considered**
Right now trying copy path to .tsx in to .tmx but sometimes save doing case from GUI like tileset parameters saved in .tmx
Thats why bad workflow around class/type: https://github.com/mapeditor/tiled/issues/4018#issuecomment-2303018079
Confirmed here: https://github.com/mapeditor/tiled/issues/4018#issuecomment-2275449399
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 comparing the existing GUI tileset export workflow with the requested .tsx import behavior, then read the linked discussion in issue 4018 for the class/type and .tmx concerns. Done means a user can import an existing .tsx tileset through the GUI without recreating it or having its parameters incorrectly saved into the .tmx.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100