| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| | |
Currently translated at 100.0% (39 of 39 strings)
|
| |
| |
| |
| | |
Currently translated at 87.7% (272 of 310 strings)
|
| |
| |
| |
| | |
Currently translated at 84.8% (263 of 310 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (39 of 39 strings)
|
| |
| |
| |
| | |
Currently translated at 97.4% (38 of 39 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (18 of 18 strings)
|
| |
| |
| |
| | |
Currently translated at 94.5% (293 of 310 strings)
|
| |
| |
| |
| | |
Currently translated at 84.5% (262 of 310 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (7 of 7 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (18 of 18 strings)
|
| |
| |
| |
| | |
Currently translated at 93.8% (291 of 310 strings)
|
| |
| |
| |
| | |
Currently translated at 80.9% (251 of 310 strings)
|
| |\ |
|
| | |\
| | | |
| | | | |
add more compatibility for Slackware
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Currently translated at 100.0% (39 of 39 strings)
|
| | | |
| | | |
| | | |
| | | | |
Currently translated at 85.1% (264 of 310 strings)
|
| |/ /
| | |
| | |
| | | |
Currently translated at 92.5% (287 of 310 strings)
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Currently translated at 97.4% (38 of 39 strings)
|
| | | |
| | | |
| | | |
| | | | |
Currently translated at 81.9% (254 of 310 strings)
|
| |/ /
|/| |
| | |
| | | |
It looks like the newer version does not like the window workspace assignment to be "-1" any more, it starts to lose it's mind and treat windows really weird now. Just use workspace 0 instead for now, and hope that Fluxbox continues to respect the window "sticky" settings for the forseeable future.
|
|/ /
| |
| |
| | |
the various options that are available.
|
| |
| |
| |
| | |
device detection routines.
|
| |
| |
| |
| | |
Currently translated at 100.0% (39 of 39 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (39 of 39 strings)
|
| |
| |
| |
| | |
Currently translated at 89.0% (276 of 310 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (39 of 39 strings)
|
|\ \ |
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
getting there.
Also commit a simple "test" app which can be modified/used to test out individual library classes as needed.
|
| |
| |
| |
| | |
lumina-open file dialog. Now it will always be listed in the preferred applications list, and with the "[default]" tag at the beginning of the name.
|
| |
| |
| |
| | |
This will be a replacement for the current LuminaX11 class usage in the desktop, with a generic Qt5 API that talks to the X11/Wayland subsystems in the background.
|
| | |
|
|\ \
| | |
| | | |
Bugfix taskmanager
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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().
|
|/ /
| |
| |
| | |
client message asking it to take focus properly as well.
|
| |
| |
| |
| |
| | |
The NativeWindow intermediary seems to be working really well, now just to start adding the the various event detection parsing in to modify that object on-demand.
There is still a window focus issue too - the setActive routine is not properly setting that window to have focus yet - need to examine further.
|
| |
| |
| |
| |
| |
| | |
class for setting/announcing changes to native windows on the system. This allows the WM class (XCB/Wayland-specific) to simply adjust each window object as needed, and the interface (pure Qt) will automatically adjust as needed.
NOTE: Still need to adjust the LXCBEventFilter to use this new class, but the root window and rootsubwindow classes are all setup to use it.
|
|/
|
|
| |
functional, with 2-way create/show/hide/close detection. Windows do not detect/resize as needed yet though.
|
|
|
|
| |
While not fully up to where the current contextmenu for Lumina is yet, it can be used for logging out, locking the screen, and launching commands (so far - will gradually add back in the other plugins/functionality later after these steps are used for more testing of other components).
|
| |
|
|\ |
|
| |
| |
| |
| | |
Currently translated at 100.0% (7 of 7 strings)
|
| |
| |
| |
| | |
Currently translated at 94.8% (37 of 39 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (39 of 39 strings)
|
| |
| |
| |
| | |
Currently translated at 81.6% (253 of 310 strings)
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Get the new LShortcutEvents class setup and functional. This is what converts the key presses and mouse clicks into a format that can be scanned for user-defined shortcuts to do things in the session.
NOTES:
The format of the keys.conf files uses "keycodes" (in ascending order") delimited by "+" to make the settings searchable and non-ordered-specific.
Example:
[strict]
22+37+64=logout
This is a shortcut for [L_Ctrl (37), L_Alt (64), Backspace (22)] and it will trigger the start of the logout procedures.
The "strict" section (and it's alternative "desktop" section) determine priority of the shortcut (strict is always evaluated, desktop is only evaluated if the desktop has focus and there is no corresponding "strict" shortcut).
|