How do I disable mouse magnet on middle edge with multi monitors?

1

Answer #: 1

There is a setting for it in Displays:

You may still get the behaviour if you have a launcher on the right monitor, so use the “Launcher Placement” option to select having your launcher on only the left screen. The stickyness between the screens is required for it to be easy to retrieve the launcher there.

You might need to log out and back in (or restart) for the changes to take effect.

Answer #: 2

The “hang” is a feature to make it possible to use the launcher in multi-monitor setups when it’s set to auto-hide. It can be configured using gconf-editor. The relevant keys are

/apps/compiz-1/plugins/unityshell/screen0/options/stop_velocity, and

/apps/compiz-1/plugins/unityshell/screen0/options/overcome_pressure

Recommended settings to minimize the effect are:

overcome_pressure=1 stop_velocity=20

These settings do not completely stop the mouse from sticking, but makes it less likely...

0 0
2

In Windows 8.1 Update 1, if you have multiple monitors, you may have observed a strange behavior of the mouse pointer. When you try to move the mouse pointer across to the other monitor, it sticks at the edge of the screen. If you move the mouse pointer fast, it goes over successfully to the other display. This is a not a bug, it's a feature. Let's see how to fix it.

Windows 10 users, please refer to the following article: MouseMonitorEscapeSpeed (Mouse pointer stickiness) fix for Windows 10

The problem I described above of mouse pointer stickiness can be best described by this video:

Video credits: Antoine Pham

This sticking of the mouse cursor on the right edge of monitor 1 and the left edge of monitor 2 (shared edge) is a feature to make the charms bar and scroll bars easier to use. Luckily you can disable it.

Open Registry Editor (see how) Go to the following key: HKCU\Control Panel\Desktop

Tip: You can access any desired Registry...

0 0
3

I spoke with DBO in #ubuntu-desktop, and he assured me this is by design.

When I use multiple monitors, I'd expect a smooth transition of the mouse from screen to screen.

Instead the mouse pauses briefly, presumably to allow the reveal of the launcher. However, even if I go slow so the launcher does not show, then I am stuck in this position and have to move my mouse much further to get it to the other screen.

This is really hard to get used to, and perhaps needs some refinement.

I'd prefer to see the mouse pass through most of the time, and only on very direct behavior, would the launcher be shown. Its also really unclear to me why it also stops while going left->right since there is nothing to reveal.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion:...

0 0
4

The "hang" is a feature to make it possible to use the launcher in multi-monitor setups when it's set to auto-hide. It can be configured using gconf-editor. The relevant keys are

/apps/compiz-1/plugins/unityshell/screen0/options/stop_velocity, and

/apps/compiz-1/plugins/unityshell/screen0/options/overcome_pressure

Recommended settings to minimize the effect are:

overcome_pressure=1 stop_velocity=20

These settings do not completely stop the mouse from sticking, but makes it less likely it will do so. You can reduce stop_velocity further if you want.

Possibly also /apps/compiz-1/plugins/unityshell/screen0/options/reveal_pressure. The latter can be configured more easily in System Settings -> Appearance ->...

0 0
5
...
0 0
6
REM This is used for adding comments to your files, and tells the joystick to ignore any lines in the joystick file that star with REM. RATE 30 How fast characters should be sent to the computer. You'll find that different sims on your computer will differ in how responsive they are to characters being sent to it from your controllers. A value of 30 means that characters should be sent every 30 milliseconds. You can put in what you want here for the value - I always start at around 60 and lower it until I see problems. USE TQS or USE WCS Tells the joystick that you have a throttle and you want to use it. USE RCS Tells the joystick that you have rudders and you want to use them. USE NOMOUSE Tells the joystick that you don't want to use the mouse on the TQS throttle. This way, you can program the mouse knob on the throttle with statements as you would any other hat or button. USE MTYPE A3 Tells the joystick to use the TQS throttle mouse to emulate your normal mouse, and the A3 part...
0 0