When re-linking missing tilesets: 1) open where it originally found the tileset, 2) provide an option to change the path in the same way for all missing tilesets
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
1) When locating/re-linking missing tilesets, it doesn't open the filepath where Tiled thinks the tileset is located - even though it _shows_ the filepath to the right of the tileset file name.
2) When I'm re-linking tilesets, I'm often re-linking an entire folder of them that I moved. They are all together, but I have to relink them all individually, which is a lot of time.
Solution I'd like for 1) It would make sense to me and save time if Tiled would open the folder that is showing to the right of the tileset file name. In most cases, the tileset has not moved very far.
Solution I'd like for 2) It would save time and be **much** simpler to have an option to change the file paths of all of the missing tilesets in the same way at once, instead of having to re-link all the tilesets in a single folder individually.
Alternatives:
Never reorganizing any tilesets, and/or setting aside entire work days to relink tilesets when my larger tileset sources (such as Gather) reorganize their Githubs. I wish I had a better one!
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 the missing-tileset re-linking workflow and the UI that displays each tileset's filepath. Check how the folder chooser is initialized, then identify how a shared path change could apply to multiple missing tilesets. Done means the chooser opens at the displayed location and one operation can relink all missing tilesets consistently.
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
- Mostly clear
- Newbie friendliness
- 38/100