 |
I'm not really sure what you mean - are you saying you need to left-click to finish the drag operation? |
 |
Grrrr, now when I try and repro it, it isnt doing it - I`ll be back here with the exact steps when it does it again. |
|
|
1. Select an item. 2. Left-click it and drag it. While dragging, click the right mouse button. 3. Release the item. 4. Left-click it again and it will jump back to where it was. It's as if the accidental right-click while dragging queues up an undo which occurs the next time you left-click. This also happens if you're dragging a brush face to resize it. |
|
|
Ok, I can see it now, when right-clicking you're basically interrupting the operation and the object data is not "frozen" in that position. |
|
|
ah, so I wasnt going mad then... |
|
|
I confirm for me at least, that this is fixed in 1.4.0pre. |
|
|
When I right-click during dragging (brush or item), the object goes back to its start position immediately, and the drop-down menu that you get when you right-click appears. Ditto for resizing brush sides. Is this the expected behavior? I was expecting the right-click to be ignored. |
|
|
This is till happening with 1.4.0, when I get the time I will build a very small test map so I can pin down exactly when/where it does it. |
|
|
This is still happening with 1.7.1 |
|
|
Confirmed. The actions in my previous note are still happening. |
|
|
This is still happening in the latest version 1.7.3 |
|
|
Still happening in 1.8.1 |
|
|
This is happening in 2.0.2 and its worse than ever. 1. shift LMB to select an item, eg a light entity 2. while holding the LMB drag the entity to a new location/ 3. let go of the LMB and the entity snaps back to its original location. |
|
|
This was caused by the DeferredMouseMotion callback pending in the background, kicking in later, when the manipulation phase already started. It can be reproduced by moving the mouse and "on the go" left-clicking the object to drag it around. As soon as the mouse cursor stops for a little moment the idle callback kicks in and sends stale coordinates to the XYWnd's mouse motion handler. |
|
|
Removed the DeferredMouseMotion handler from both CamWnd and XYWnd. |
- Anonymous
