editor: Unable to move object after rotating it

[dnl-k]

Which resource(s) have this problem? editor

Describe the bug After rotating any object once while holding one of the rotate modifier keys (lctrl, rctrl), you are no longer able to move any object

To Reproduce

1. Launch editor
2. Place any object
3. Move that object, works as intended
4. Rotate that object using any rotate modifier key, works as intended
5. Try to move that object, it rotates instead of moving

Expected behavior It's supposed to move.

Version 1.6

[dnl-k]

This appears to only happen when you switch around the rotate modifier keybinds (which is necessary to get the old rotating behaviour as it got changed with ced470eb0ead7c48df948a17533fda8cbe656b0d)

[dnl-k]

So nobody seems to care eh

I looked into what might cause this but haven't found a real culprit yet When switching the keys in the settings around and pressing one of it down it fires the correct command, but upon releasing the key it'll fire the default command e.g. press lctrl it triggers mod_rotate_local but when releasing it, it'll trigger mod_rotate This does not appear to happen with any other key bindings when switching them around..

[Dark-Dragon]

I can't reproduce the problem. No matter which modifier I press, if I press them both at the same time or even bind both of them to the same key, I can't reproduce it, movement always returns to functional the moment no rotation modifier is held as intended.

[dnl-k]

I just completly reinstalled MTA to verify and the issue still persists for me.

Edit:

default settings:

* Commands bound to "lctrl" (down) *
Rotate Modifier World Space
Clone Drop Modifier

* Commands bound to "lctrl" (up) *
Rotate Modifier World Space
Clone Drop Modifier

mod_rotate & mod_rotate_local bindings switched:

* Commands bound to "lctrl" (down) *
Clone Drop Modifier
Rotate Modifier Local Space

* Commands bound to "lctrl" (up) *
Rotate Modifier World Space
Clone Drop Modifier

[jlillis]

I'm not able to reproduce this either. Has anyone else experienced this?

[Nico8340]

I'm not able to reproduce this either. Has anyone else experienced this?

I didn't succeed to reproduce it either.

[Nico8340]

If you could share more details about the reproduction, it would greatly help in the process of finding and fixing the error. @dnl-k

[jlillis]

As this hasn't been reproduced in several months, I'm going to close this for now.