Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S Solaar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pwr-Solaar
  • Solaar
  • Issues
  • #1701
Closed
Open
Issue created Aug 19, 2022 by Administrator@rootContributor

Usability: Rules editor hint for (Wayland) key presses

Created by: shoffmeister

Personal experience shows: people don't read the fine manual, but just do - and then are quite surprised that the "Key press" action in the Rules Editor does not have the expected effect.

Suggestion: Add a very short hint to the input section

image

that alerts users to the various challenges of doing key press (on Wayland). This is rather important, IMHO, because solaar encountering failure, e.g.,

12:25:57,373  WARNING [MainThread] logitech_receiver.diversion: cannot create uinput device: "/dev/uinput" cannot be opened for writing
12:25:57,373  WARNING [MainThread] logitech_receiver.diversion: no way to simulate key input

is typically not conveniently discoverable for users (which in itself is not ideal, IMHO).

The hint could be as simple as "Key press actions are not robust; see for details".

Then people (me) might read the readme (sooner) and eventually also the rules docs.

Assignee
Assign to
Time tracking