mirror of
https://github.com/VallierDev/uu-remote-linux.git
synced 2026-11-16 08:50:40 +01:00
* portal: mobile touch-mode drags become touch, consent asks once for it In touch mode the Android viewer sends a finger as a left-button drag at absolute positions (observed: press, mouse_move_absolute stream, release), which on GNOME selects text instead of scrolling. SelectDevices now also asks for the touchscreen type where AvailableDeviceTypes offers it, and a drag from an Android/iOS controller (controller_platform 2/3) that follows absolute motion is replayed as one finger through NotifyTouch* or EIS touch, so the desktop scrolls and taps as on a touch screen. Relative motion (the trackpad mode) and every other viewer keep mouse buttons. A consent saved before this restores keyboard and pointer only. The first mobile drag then asks the host once per run in the background (GNOME's share dialog, also visible on the phone; the consent timeout closes it) and swaps the new session in only when it grants the touchscreen for the same monitor and size. The saved consent is never removed beforehand. UU_TOUCH_INPUT=0 keeps mouse drags and never asks. * input: type mobile IME text as portal keysyms on Latin GNOME layouts Each mobile text_input was set as the clipboard and pasted with Shift+Insert, which VTE terminals bind to the PRIMARY selection: text typed from the phone into a terminal pasted whatever was last selected (observed: a selected line of box-drawing characters for every letter). When GNOME's active input source (first of mru-sources) is a Latin xkb layout, printable ASCII, newline and tab now go through NotifyKeyboardKeysym, where Mutter picks the key and Shift level of the active layout. Other text, IBus engines, KDE and EIS sessions keep the clipboard paste, which no longer replaces the clipboard for plain typing. * portal test: accept libei before 1.3 rejecting a touch outside one of two regions libei 1.2 (Ubuntu 24.04, CI) accepts a touch only inside every region of the device; 1.3.0 checks any region. The harness device also carries a region for another screen, so the older library rejects the touch with a client-bug diagnostic. A real one-stream session has one region.