| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
(pauses/delays the session init)
|
|
|
|
| |
lumina-mediaplayer to one that exists in more themes
|
|
|
|
| |
"ExternalProcess" class can provide a better way of doing that on a per-process basis.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
working fine now.
|
| |
|
|
|
|
| |
high-DPI screens.
|
|
|
|
| |
(application menus, etc). Now we are starting to see the better performance from this system... :-)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
match what is used in lumina-config.
|
| |
|
| |
|
|
|
| |
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.
|
|
|
|
| |
date/time formats.
|
|
|
|
| |
Qt5 auto-scaling set.
|
|
|
|
| |
This needs to be set for applications, but not the desktop itself (since there are so many pixel-specific calculations that need to be performed).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Add calls to setToolButtonStyle() when LTaskButton is created.
LTaskManagerPlugin::OrientationChange() already has calls to set the button style when orientation is changed, but this is overwritten in LTaskButton::UpdateButton().
|
|
|
|
| |
tinkering with it)
|
| |
|
|
|
|
| |
of text depending on size limitations.
|
|
|
|
| |
.desktop files.
|
|
|
|
| |
file/list changes*.
|
|
|
|
|
|
| |
battery plugin.
Also, add a green background to the battery plugin when the charge is 100% and still plugged in.
|
| |
|
|
|
|
| |
"audioplayer": This is panel-based implementation of the desktop plugin with the same name. Allows the user to load/play audio files directly from the desktop session without loading any external applications.
|
|
|
|
|
|
|
| |
1) Dismantle the Lumina library completely.
2) Setup lots of small subproject files (.pri) for the individual classes within the old library.
3) Move all the Lumina binaries to use the new subproject files
4) Split up the LuminaUtils class/files into LUtils and LDesktopUtils (generic utilities, and desktop-specific utilities)
|
|
|
|
|
| |
1) Add a new .pri for loading just that class (works stand-alone)
2) Setup the lumina-desktop to use the new build framework for including that class.
|
|
|
|
| |
other than the background color based on battery level.
|
|
|
|
|
|
| |
1) for the "low" battery icon, move it down to the 5-20% range instead of 20-50%.
2) When battery is between 0-5%, change the background color of the icon to red in addition to the "warning" battery icon.
3) Play an audio file when the battery drops to the 0-5% range( <Lumina Share directory>/low-battery.ogg), if the file exists.
|
|
|
|
| |
This reduces the number of widgets in the stack by 1, and seems to help performance a bit.
|
|
|
|
| |
the new changes.
|
| |
|
|
|
|
|
|
| |
This impacts almost all tools/utilities within Lumina - please test (passed internal tests so far).
This cleans up a lot of the backend XDG compliance class, moving lots of functionality into child functions of the XDGDesktop class and ensuring that they get cleaned up more regularly/properly. This *seems* to make the desktop startup a lot faster, even if the overall memory savings are slight (so far).
|
|
|
|
| |
start menu.
|