A while ago selmiak has requested that when objects and characters are moved by keyboard in the room editor, the editor would also display their coordinates, similar to how they are displayed when being dragged by a mouse.
https://github.com/adventuregamestudio/ags/issues/984
I tried to make this work with a small change
https://github.com/adventuregamestudio/ags/pull/2229
But that immediately raised a question of when to hide this extra label with coordinates on them.
The problem is, when you move with a mouse the hint may stay for as long as the mouse button is down.
But with keyboard, when arrow is down the object will keep moving. User may want to stop for a while to think, or check something. If I make the hint disappear in this moment, then user will have to hit an arrow once again to make it reappear, but will move object away from its location at the same time. This makes things uncomfortable, and I am concerned that this will defeat the purpose of the fix.
There are following options that came to mind (there may be others which i missed):
1. Make coordinates display all the time so long as object is selected;
2. Keep coordinates display after it's been moved by keys until it's moved by mouse or deselected;
3. Hide this hint by a timer run after user released the moving keys (but then some users may argue that timeout is not enough).
I cannot decide, so post here to ask for opinions.
Option 1) is the simpliest, but I wonder if users won't like how it looks like.
If you like to see how this works,
there's a temp build with this feature (3.6.1 based): https://cirrus-ci.com/task/6302126616346624
here's a video recorded:
https://github.com/adventuregamestudio/ags/pull/2229#issuecomment-1810476782
Maybe add a toggle key, so that the label is always shown when the toggle is on, no matter whether you are moving an object or the currently active object is stationary?
This way, you can toggle it off so that the label is never shown, as sometimes people may not want to see it for some reasons.
This is already in 3.6.1
@Crimson Wizard
Probably was overthinking this problem.