vasilito
f31522130f
Build system (5 gaps hardened): - COOKBOOK_OFFLINE defaults to true (fork-mode) - normalize_patch handles diff -ruN format - New 'repo validate-patches' command (25/25 relibc patches) - 14 patched Qt/Wayland/display recipes added to protected list - relibc archive regenerated with current patch chain Boot fixes (fixable): - Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset) - D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped) - redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped) - daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch) - udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async) - relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs - greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait) - greeter-ui: built and linked (header guard unification, sem_compat stubs removed) - mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps - greeter config: removed stale keymapd dependency from display/greeter services - prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified Unfixable (diagnosed, upstream): - i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort - kded6/greeter-ui: page fault 0x8 — Qt library null deref - Thread panics fd != -1 — Rust std library on Redox - DHCP timeout / eth0 MAC — QEMU user-mode networking - hwrngd/thermald — no hardware RNG/thermal in VM - live preload allocation — BIOS memory fragmentation, continues on demand
36 lines
1.8 KiB
ReStructuredText
36 lines
1.8 KiB
ReStructuredText
.. _middle_button_emulation:
|
|
|
|
==============================================================================
|
|
Middle button emulation
|
|
==============================================================================
|
|
|
|
Middle button emulation provides users with the ability to generate a middle
|
|
click even when the device does not have a physical middle button available.
|
|
|
|
When middle button emulation is enabled, a simultaneous press of the left
|
|
and right button generates a middle mouse button event. Releasing the
|
|
buttons generates a middle mouse button release, the left and right button
|
|
events are discarded otherwise.
|
|
|
|
The middle button release event may be generated when either button is
|
|
released, or when both buttons have been released. The exact behavior is
|
|
device-dependent, libinput will implement the behavior that is most
|
|
appropriate to the physical device.
|
|
|
|
The middle button emulation behavior when combined with other device
|
|
buttons, including a physical middle button is device-dependent.
|
|
For example, :ref:`clickpad_softbuttons` provides a middle button area when
|
|
middle button emulation is disabled. That middle button area disappears
|
|
when middle button emulation is enabled - a middle click can then only be
|
|
triggered by a simultaneous left + right click.
|
|
|
|
Some devices provide middle mouse button emulation but do not allow
|
|
enabling/disabling that emulation. Likewise, some devices may allow middle
|
|
button emulation but have it disabled by default. This is the case for most
|
|
mouse-like devices where a middle button is detected.
|
|
|
|
libinput provides **libinput_device_config_middle_emulation_set_enabled()** to
|
|
enable or disable middle button emulation. See :ref:`faq_configure_wayland`
|
|
and :ref:`faq_configure_xorg` for info on how to enable or disable middle
|
|
button emulation in the Wayland compositor or the X stack.
|