Stuck mouse glitch

[jdude]

For some reason the editor tends to do this to me every once and a while. I will be using the 3d camera and for some reason as long as the Dark Radiant window is open, the mouse wont get out of the 3d view box. If I hit tab though it gets out. But sometimes when looking around a 2d view using the right mouse button and moving, the mouse can get stuck, and when I alt tab to a different program and then move the cursor over Dark Radiant it gets stuck again and if I shake the mouse around it keeps centering on where it is stuck. I've had to quit when it does this because tab does nothing.

[sparhawk]

Did you try the right mouse button? Personally I find it really annoying that I have to toggle the movement by using the right mouse button to enable/disable it. I tend to forget it, and then I move the camera widly around because of it. I would prefer it if the movement is active as long as the button is pressed.

[angua]

Did you try the right mouse button? Personally I find it really annoying that I have to toggle the movement by using the right mouse button to enable/disable it. I tend to forget it, and then I move the camera widly around because of it. I would prefer it if the movement is active as long as the button is pressed.

This is already implemented, you can change the behaviour in Preferences->Camera.

[greebo]

For some reason the editor tends to do this to me every once and a while. I will be using the 3d camera and for some reason as long as the Dark Radiant window is open, the mouse wont get out of the 3d view box. If I hit tab though it gets out. But sometimes when looking around a 2d view using the right mouse button and moving, the mouse can get stuck, and when I alt tab to a different program and then move the cursor over Dark Radiant it gets stuck again and if I shake the mouse around it keeps centering on where it is stuck. I've had to quit when it does this because tab does nothing.

This is because the renderer is too slow and can't keep track of the mouse pointer.

 

During toggled freelook mode, the mouse pointer is "caught" and kept at the middle of the window after each movement. This is usually happening very fast and the mouse pointer can never go out of the window bounds. However, if the rendering takes too much time (or if you're moving the mouse really fast), the user is able to move the mouse out of the window bounds before DarkRadiant gets a chance of moving it back to the window.

 

Once the mouse pointer is "out of window bounds", no more mouse events get sent to the camera window and it will sit there, doing nothing.

 

Not much you and me can do about it, except this:

- Hit Alt-Tab to leave the app, DarkRadiant will detect this and leave the freelook mode.

- Try to move the hidden mouse back in over the camwindow, flying blind so to say. Once you see the cam moving again, hit RMB.

- Use the non-toggleable freelook mode as last resort.

[sparhawk]

Once the mouse pointer is "out of window bounds", no more mouse events get sent to the camera window and it will sit there, doing nothing.

 

You can use CaptureMouse (or some such) to avoid this. Don't know if this is available in DR as you use GTK, right? But it definitely is availabe in Win32, so maybe they have a wrapper for that.

 

http://www.codeproject.com/gdi/mousecapture.asp

[sparhawk]

This is already implemented, you can change the behaviour in Preferences->Camera.

 

Cool! Thanks!

[greebo]

You can use CaptureMouse (or some such) to avoid this. Don't know if this is available in DR as you use GTK, right? But it definitely is availabe in Win32, so maybe they have a wrapper for that.

 

http://www.codeproject.com/gdi/mousecapture.asp

This is Windows-only, from the looks of it. But I'll have to check whether GTK provides a separate "on mouse leave" event for a given widget. This event would be exactly what we would need.

[OrbWeaver]

In my opinion we should ditch the toggle-mouse altogether and provide a more standard drag-based interface. Toggle interfaces are generally poor design anyway (since things behave differently in different "modes"), and this seems to require some hackery to achieve.

[greebo]

I personally favour that toggle mode. I find it much more convenient than the drag-solution, it makes it easier to de-select and select things and do other stuff without having to keep that stupid RMB down all the time.

[sparhawk]

No matter how you do it, you will still need that capture event. But I find togglable interfaces not very intuitive.

[Fidcal]

If the camera view routine cannot detect that the mouse has moved away because it was busy rendering, can instead DR capture the mouse over the grid view somehow and use it to disconnet the camera thing? I put that extremely clumsily but hope you know what I mean. I can't tell if my friend's left the house but his other friend can ring me when he arrives there.

 

Wot I normally do is keep thrashing different buttons and throw the keyboard about and curse and swear. This always works for me.

[SneaksieDave]

I also have come to prefer toggle mode and would hate to see it go away (and I was one of those originally arguing against it!).

[jdude]

Howdy, I just wanted to let you guys know that I found a solution for the mouse getting stuck on the ortho views. if you hold tab for about 5 seconds, it resets the mouse. I thought it only worked for the 3d view but I was wrong

[Komag]

I have just experienced this bug for the first time! It got fixed by Alt-Tab'ing to another window, then going back to DR.

 

But then I searched around the forums and found this thread, and I got it in my head to try to reproduce the problem. This time the problem was a bit different, and it would never fix, so I had to close DR.

 

I really like toggling 3D movement, but if that capturemouse fix mentioned above can be implemented it would be good. However, I've never gotten the problem before now, so I think it could actually just be lived with if necessary, since it's so rare an pretty much benign.

[jdude]

I think it may be more prominent in larger maps which cause DR to slow a lot.