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
  • #1995
Closed
Open
Issue created Feb 17, 2023 by Administrator@rootContributor

Originating Device Condition Rule

Created by: cbeley

Information

Currently, there appears to be no way to write a rule that applies only to a specific originating device. In the case of the Pop Keyboard and mouse, there is a conflict for diversion of the Open Emoji Panel (0108) button, which emits the same code when pressed on both the keyboard and the mouse.

It'd be nice to have the button on the mouse perform a different action than on the keyboard.

Describe the solution you'd like I'm assuming there is no way to change the code that is emitted on the mouse. However, if it were possible to write a rule that was something like when originating device is "pop mouse" and key is Open Emoji Panel (0108) (pressed), I think that would do the trick.

Describe alternatives you've considered I did play a bit with trying to set the button to be the gesture button, then writing a divert rule for that. I assume this doesn't work because all the gesture button diversion does is try to divert "Open Emoji Panel (0108) (pressed)tomouse gesture button`.

Additional context

Other than for the pop mouse and keyboard, I'm not sure how much usefulness this feature would have otherwise. It's purely a consequence of Logitech deciding to use identical codes on both the mouse and keyboard.

Other than this issue, the mouse and keyboard, as well as diversion of all the special keys, works perfectly for me.

Assignee
Assign to
Time tracking