mapeditor / mapeditor/tiled

Object Inspector autocompletion

Open
#225 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

usability
Dominant language
C++
Stars
12.9k
Forks
2k
Avg merge
4h 27m
Merged PRs (30d)
8

Description

Could be great if Object Inspector can have a "smart" autocompletion. Just like Freemind does with his elements Tags.
For example: If we had any object with a property named "style", and we created a new object, we can SELECT "style" instead of writing it (just like intellisense usually does).
Another cool example: If we had any object with this set of properties:
style: rough
material: wood

and other object with these properties:
style: soft
material: metal

we have TWO autocompletions for property field: style and material.
so, we have TWO autocompletions for EACH property at the VALUE field as well, for example: if we wish to write the value of a "style" property, we have two default options "soft" and "rough", so... if we want to set the value of "material" we have "wood" and "metal".

Every time that we change something at object properties, the internal "intellisense dictionary" must be updated. To discard inexistences and adding new entries.

This is relatively simple to do, and very useful, because really helps to filter sintax errors on properties and values.

Even, if we had this, could be VERY useful (in certain circumstances) to export and import the current autocompletion state (just like default types does, but without need to have assigned colors).

I think that could be a really great feature. =)

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

The issue targets the Object Inspector but names no files, tests, or code entry points. Start by locating the Object Inspector implementation and reviewing how object properties and values are edited. Done should include updated property and value suggestions, dictionary updates after edits, and a decision on whether importing and exporting the completion state is in scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.