mapeditor / mapeditor/tiled

Keep class properties closed when default in custom properties that are classes.

Open
#3,489 0 comments 0 reactions 0 assignees View on GitHub

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.**
If using custom properties that are classes, currently they are always fully shown in Tiled. You can click the small arrows to close the class and the subclass properties, but each time you go back to an object, they will have been re-opened. This can take up quite a lot of screen space, making scrolling or a constant closing of properties a cumbersome task.

**Describe the solution you'd like**
That classes/sub-classes remain closed when they do not have any values edited that differ from the default (as in when they get the bold text).

How it is now:
![asisnow](https://user-images.githubusercontent.com/17771475/193998940-f6b97ca5-949d-4571-888c-b236d95a1090.png)

How it would be:
![asisshould](https://user-images.githubusercontent.com/17771475/193998772-03d64257-1531-4dc0-a37a-4351682736d3.png)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named in the issue. Start by locating the Tiled editor logic that displays custom class properties, then check how edited values are distinguished from defaults. Done means class and subclass properties with only default values are closed when revisiting an object, while properties with differing values remain open.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.