mapeditor / mapeditor/tiled

Allow use of number hotkeys when a tile layer is not selected

Open
#3,170 0 comments 1 reaction 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

_Using Tiled 1.7.2, Linux._

__Problem:__

I tried to bind the number keys to the object shape tools (CreateRectangleObjectTool, CreatePointObjectTool, etc.) and was very confused why they worked just fine in the Tile Collision Editor with a tileset open, but silently failed to work with a tile*map* open and an object layer selected.

After a bit of searching I found that [the number keys recall your saved tile stamps when editing a tile layer](https://doc.mapeditor.org/en/stable/manual/keyboard-shortcuts/#when-a-tile-layer-is-selected).

__Feature Request:__

Make the recall-tile-stamp bindings on the number keys not steal inputs outside of their context (tile layer selected)

__Other Info:__

* Binding something to the number 1 key works everywhere except the tilemap view.
* Binding a built-in tool to the number 1 key fails silently in the tilemap view.
* Binding any action or a custom tool to the number 1 key fails and prints "`QAction::event: Ambiguous shortcut overload: 1`" to the console, _every other time_ I press the key or continuously if I hold the key down.

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

Reproduce the shortcut behavior in the tilemap view with an object layer selected, then trace how saved tile-stamp bindings are handled for a selected tile layer. Done means number-key bindings for tools or actions work outside tile-layer editing without producing ambiguous shortcut warnings.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.