219
edits
(→Related content: + Subsections; + Link: Bindings; +- Template:Forum → Template:Forum link) |
|||
Line 529: | Line 529: | ||
It can be useful to tell X to ignore the mouse so that it doesn't affect the main X pointer. This can be done with: <code>xinput --set-prop <id> "Device Enabled" 0</code>. Normal X handling of the mouse can be restored with <code>xinput --set-prop <id> "Device Enabled" 1</code>. (One can also use the name of the mouse instead of <code><id></code>.) | It can be useful to tell X to ignore the mouse so that it doesn't affect the main X pointer. This can be done with: <code>xinput --set-prop <id> "Device Enabled" 0</code>. Normal X handling of the mouse can be restored with <code>xinput --set-prop <id> "Device Enabled" 1</code>. (One can also use the name of the mouse instead of <code><id></code>.) | ||
On Devuan Linux, one can use a udev rule to ensure that the mouse can be read and written by flightgear (usually they are only accessible to root): | On Devuan Linux, one can use a udev rule to ensure that the mouse can be read and written by flightgear (usually they are only accessible to root): | ||
* Create a file <code>/etc/udev/rules.d/90-fgmouseextra.rules</code> containing a single line <code>KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0666"</code>. | |||
* Reboot or run <code>udevadm control --reload-rules</code>. | |||
[Note that i know almost nothing about udev, and it's entirely possible that this represents a huge security flaw, so use with caution.] | |||
[The information above is based on the forum thread https://forum.flightgear.org/viewtopic.php?t=32750 and Torsten Dreyer's original email https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23171.html.] | [The information above is based on the forum thread https://forum.flightgear.org/viewtopic.php?t=32750 and Torsten Dreyer's original email https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23171.html.] | ||
== Related content == | == Related content == |
edits