| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
enabled (too many false-positives from the GPU acceleration verification routine).
|
| |
|
|\ |
|
| |\
| | |
| | | |
Summary: Fix the workspace switcher panel plugin when using a keyboard shortcut to change the workspace.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The workspace information wasn't getting updated in the workspace-switcher-panel-plugin(wsp)
when the workspace was changed via keyboard-shortcut, for example <ctrl-F2> etc.
Specifically, the tooltip for the wsp would show the incorrect number for the current workspace.
Details:
The wsp menu always did indicate the correct workspace number because the user has to click
on the wsp to display the menu. The click-action sends a signal which updates the workspace info
in the menu. But, the tooltip doesn't necessarily display the correct workspace number unless the
user clicks on a workspace in the menu.
To reproduce the problem:
1. The current workspace is workspace 1.
2. Change to a different workspace via keyboard-shortcut, for example <ctrl-F2>.
3. Mouse-hover over the wsp and the tooltip displays the previous workspace number which is incorrect.
Code Changes:
The code changes are small and limited to the two source files in the desktopswitcher subdir.
|
| | |
| | |
| | |
| | | |
Currently translated at 100.0% (320 of 320 strings)
|
| | |
| | |
| | |
| | | |
Currently translated at 99.0% (317 of 320 strings)
|
|/ / |
|
| |
| |
| |
| | |
to another on the first start of the desktop, and enable that migration for single-monitor arrangements.
|
| |
| |
| |
| | |
Currently translated at 100.0% (320 of 320 strings)
|
| |
| |
| |
| | |
Currently translated at 97.5% (39 of 40 strings)
|
| |
| |
| |
| | |
Currently translated at 78.7% (252 of 320 strings)
|
| |
| |
| |
| | |
the new port files.
|
| |
| |
| |
| | |
Currently translated at 98.4% (315 of 320 strings)
|
| |
| |
| |
| | |
Currently translated at 98.1% (314 of 320 strings)
|
| |
| |
| |
| | |
Currently translated at 96.8% (310 of 320 strings)
|
| |
| |
| |
| | |
Currently translated at 94.6% (303 of 320 strings)
|
| |
| |
| |
| | |
Currently translated at 81.2% (260 of 320 strings)
|
|/
|
|
| |
Currently translated at 100.0% (40 of 40 strings)
|
|
|
|
| |
Currently translated at 77.8% (249 of 320 strings)
|
|
|
|
| |
Currently translated at 95.0% (38 of 40 strings)
|
|
|
|
| |
Currently translated at 100.0% (18 of 18 strings)
|
|
|
|
| |
match what is used in lumina-config.
|
|
|
|
| |
Currently translated at 77.1% (247 of 320 strings)
|
|
|
|
| |
Currently translated at 57.1% (4 of 7 strings)
|
|\ |
|
| |
| |
| |
| | |
Currently translated at 100.0% (320 of 320 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (320 of 320 strings)
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Currently translated at 100.0% (320 of 320 strings)
|
| |
| |
| | |
Fix some leftover whitespace.
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
1) Unify the terminology for all the "leave" options (power off, restart, log out)
2) Remove some superfluous text from the system dashboard plugin menu.
|
| | |/
| |/|
| | |
| | | |
Currently translated at 96.8% (310 of 320 strings)
|
| |/
| |
| |
| | |
Currently translated at 96.5% (309 of 320 strings)
|
| | |
|
| | |
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | | |
Currently translated at 89.3% (277 of 310 strings)
|
| | |/
| |/|
| | |
| | | |
This will be used to determine whether to automatically show the /media files on the desktop.
|
| |\| |
|
| | |
| | |
| | |
| | | |
date/time formats.
|
| |/
|/|
| |
| |
| | |
Now whenever a screen is added/changed it will print out the physical/logical DPI values into the log, and if a logicalDPI (X or Y) is greater than 110 it will enabled the Qt5 auto-scale functionality.
Note: My 1080p laptop monitor has a logical DPI of ~96, but a physical DPI of ~150 and the Qt5 auto-scale stuff is based on physical DPI (so things got massive on a normal-res screen). I am leaving the DPI print-out in the logs for now so that if we run into any other monitors where the logicalDPI>110 rule is invalid we can view/tweak the rule really easily.
|
|\| |
|
| |
| |
| |
| | |
"file" is actually a symlink somewhere else on the system (will just remove the symlink)
|
| |
| |
| |
| | |
Changelog: yes
|