Is there a way to set a time delay when you move your mouse to an active border before it switches to the next virtual screen? I would like the system to wait for 2 - 3 seconds before it changes screens.
Actually no, you cannot set a time delay before switching; you can however choose to switch when the mouse is clicked instead of moved (go to the "Settings/Virtual screen" option of the VDT menu).
However, your suggestion is quite interesting and we will try to implement it; thank you.
Thanks for the response. I as aware of the switch with mouse setting. I look forward to the addition of this feature.
Just as a quick explanation, the primary reason for this is more and more applications are adding the ability to dock on a border and then auto hide the dock. When you go to that border for the docked app. you end up switching virtual desktops. This delay would prevent that from happening right away.
Thanks again for your efforts, keep up the good work.
When displaying the virtual screen properties window, the "Mouse switch mode" list has now a "Motionless mouse" option; when enabled, you can switch by moving the mouse on the border and then wait for 2 seconds without moving (any mouse move will reset again the 2 seconds time-out).
The 2 seconds delay cannot be changed using the interface; you can however change it using the registry editor. Go to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesR2d2KernelAuthorityParameters and create a REG_DWORD value called MouseStayDelay; give the delay in milliseconds (R2d2 Kernel Authority service must be stopped and restarted to read the new value).
Is there a possibility of checking for no movement of the cursor in one axis, rather than checking for movement in both directions, or mouse movement in general?
To try and explain better - if you move the mouse against the edge of the screen, and keep moving it in that direction, and then the desktop changes, it feels as if you've 'pushed' the screen across until it gives in. So, ideally the check would be for movement of the cursor (not the mouse) in one axis of direction - ie, if the current screen edge is right/left then the check for timer reset should be to make sure that the cursor has not moved in the x-axis (that is, it can move up and down, so long as it doesn't move off the screen edge), and if the current screen edge is top/bottom, then the check should be for movement of the cursor in the y-axis.
Hope that makes sense. Many vwm's use this method and it 'feels' right.