-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Streamline UI #2349
Comments
Moving the Unpair button just above the config panel seems to make it no less likely to be accidentally touched. Moving the light bulb elsewhere seems reasonable . What are the "top bar" options? Solaar doesn't take control of the title line. If the Quit button is removed, there is no way to stop Solaar. Using the close button for this appears worse than the situation for the unpair button. Pair and unpair are analgous and so placing them in the same location seems reasonable. Both are used only occasionally. It might be possible to ask for confirmation of unpairing. Having an add-rule button is a good idea. If the three buttons are moved to the bottom they will have to be distinguishable from the area used to enter parameters for conditions and actions. |
Yes, some systems don't have a suitable system tray application set up. By the way, why are there no icons in your screenshot? |
That's because all these screenshots are from macOS. There are quite few icons supported as is. |
This change adds an explicit button to add a new rule. Previously a new rule could only be created via context menu, which is hard is not beginner-friendly and not obvious. This change improves that. Related pwr-Solaar#2349
This change adds an explicit button to add a new rule. Previously a new rule could only be created via context menu, which is hard is not beginner-friendly and not obvious. This change improves that. Related pwr-Solaar#2349
This change adds an explicit button to add a new rule. Previously a new rule could only be created via context menu, which is hard is not beginner-friendly and not obvious. This change improves that. Related pwr-Solaar#2349
This change adds an explicit button to add a new rule. Previously a new rule could only be created via context menu, which is hard is not beginner-friendly and not obvious. This change improves that. Related pwr-Solaar#2349
This change adds an explicit button to add a new rule. Previously a new rule could only be created via context menu, which is hard is not beginner-friendly and not obvious. This change improves that. Related pwr-Solaar#2349
This change adds an explicit button to add a new rule. Previously a new rule could only be created via context menu, which is hard is not beginner-friendly and not obvious. This change improves that. Related pwr-Solaar#2349
Information
Additional context
The User interface could be cleaner with fewer distractions and a little polishment on button placement etc. Based on the various views I have the following suggestions.
Main window - device selected
The main actions here are configuration or adding rules. However, the impactful Unpair button is too prominently placed to be accidentally touched.
Key/Button Action and Key/Button Diversion only show the status of a single button at a time. It is not posible get to know the status of all buttons at once. The status needs to be visible all at once. A fixed list with the input buttons and the drop-down for the setting is much better. So far these entries are at most 10 keys MX Master and MX Keys. This also improves the situation for #2326 a little bit.
Main window - receiver selected
Rule editor
On the long run, there should be a pretty dumbed down, more graphical version of setting up rules. You know which buttons a mouse has and mainly want to configure each of them. The existing unlimited hierarchy gives too much freedom, which adds complexity with little gain. For 99,9% of the use cases it's probably over kill.
Some little improvements, which are easy to add is an improved UI with no need to find the right click menu set up some rules.
Quit rule editor dialog (pending changes)
About window
No button is necessary there. It is just an info page, which could show everything by default.
More to follow
The text was updated successfully, but these errors were encountered: