-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Processor info very big and look messy #18
Comments
What's your screen resolution? I have to well figure out how to solve the problem of a screen too low to hold all the information. Today I ran some tests for a scrolling container but I don't really like the mouse interaction since it's a popup that disappears when the mouse goes outside the name. A solution might be to selectively remove some lines until the list of information completely fits on the screen. |
I suggest you split the information into two: Basic and Extended (=Flags and Vulnerability related stuff) and optionally allow the user to disable the Extended info. |
If I choose that path, I have to set the basic info as default and add an option to enable extended info. I don't want the user to face a bug-like situation at the first extension tryout. |
Then, a cascading menu is the second option coming to mind. But, this will make the screen layout and usage more complex. |
@Anifyuli This should be fixed in the next release. When the screen is short multi-lines are stripped to a single line. If it's still not ok comment here or open a new ticket. |
I use 768P screen resolution |
Description
Processor info hover action is very big and look messy and not uniform too with other info
Steps to Reproduce
Screenshots
Environment
Logs
N/A
Additional Context
N/A
The text was updated successfully, but these errors were encountered: