Page 1 of 1

[Rseding91] [2.0.39] Map Tags cannot be moved with Shift-Click shortcut

Posted: Wed Mar 05, 2025 7:10 pm
by eugenekay
What did you do?
  • Open Remote View
  • Mouseover a Tag/icon previously placed on the map
  • Shift-Click to move the Icon
What happened?
Icon stays in place
What did you expect to happen instead? It might be obvious to you, but do it anyway!
Icon would follow the mouse cursor / move for placement
Does it happen always, once, or sometimes?
  • Since updating to 2.0.39, using Shift-Click - worked in 2.0.38 and previous
  • Tags can be moved normally via the "Move" icon in their dialog box.
  • Tags can be pipetted(using "Q") and placed on the Map
  • Click-dragging on an Icon moves the map - this has not changed.
  • Changing the Primary and Secondary binding for "Move tag" to other combinations (Right-click, Alt+Left-click, Etc) also do not work.
I have reviewed the Control settings for "left-click" and friends; I do not think I have made any changes to these, but I have not cross-checked with the Defaults.
Screenshot 2025-03-05 140528.png
Screenshot 2025-03-05 140528.png (189.07 KiB) Viewed 446 times
Thanks for reading!

Re: [2.0.39] Map Tags cannot be moved with Shift-Click shortcut

Posted: Wed Mar 05, 2025 8:26 pm
by Rseding91
Thanks for the report. This is now fixed for the next release.

Re: [2.0.39] Map Tags cannot be moved with Shift-Click shortcut

Posted: Thu Mar 06, 2025 6:14 am
by AnriMachishiro
FYI, not only the shift+left-click becomes unavailable, but also long-pressing left-click.

Re: [2.0.39] Map Tags cannot be moved with Shift-Click shortcut

Posted: Wed Mar 12, 2025 6:39 pm
by Usul
Rseding91 wrote: Wed Mar 05, 2025 8:26 pm Thanks for the report. This is now fixed for the next release.
Really? 2.0.40 release notes do not mention this here bug #664872.

Re: [2.0.39] Map Tags cannot be moved with Shift-Click shortcut

Posted: Wed Mar 12, 2025 6:56 pm
by Rseding91
Usul wrote: Wed Mar 12, 2025 6:39 pm
Rseding91 wrote: Wed Mar 05, 2025 8:26 pm Thanks for the report. This is now fixed for the next release.
Really? 2.0.40 release notes do not mention this here bug #664872.
That's the post number, not the topic number. The topic number 127287 which is referenced in the 3rd line of bug fixes in 2.0.40 changelog.