| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
bad idea)
|
| |
|
|
| |
still getting random artifacting *outside* of the window that we are painting from time to time.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
fix some connection warnings.
|
| |/ |
|
| |
|
|
| |
the Lumina2 project.
|
| |
|
|
|
|
| |
long to be mixed in with the rest of the class).
Also finish up a lot more of the conversions. Should be ready for testing now.
|
| |
|
|
| |
raw keycodes.
|
| |
|
|
| |
definition
|
| | |
|
| | |
|
| |
|
|
| |
rather than a global object (lets us use the DesktopSettings within the standalone classes in libLumina as well).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
properly getting registered for the session.
|
| |
|
|
| |
start testing and see if windows respond to the EWMH hints.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This gets the new "NativeWindowSystem" and associated Native* classes all integrated (untested)
|
| | |
|
| |
|
|
| |
finished (one last calculation to do)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
default "sample" screensaver: a "Fireflies" screensaver.
|
| |
|
|
| |
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.
|
| |
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
1) Get the RootWindow up and functional.
2) Get the lumina-desktop-unified binary functional for starting to test the various pieces (not ready yet for general use)
3) Get the start-lumina-desktop binary setup to launch the new unified binary for testing if the "--unified" flag is used.
|
| |
|
|
| |
lumina-desktop-unified build. Also finish cleaning up the compilation of the lumina-desktop-unified project - still not ready for actual testing yet.
|
| | |
|
| |
|
|
|
| |
1) Make a new "DesktopSettings" class in libLumina for managing desktop settings files. This class understands/uses a hierarchy of files (User Overrides > System Overrides > Default Settings) and layers them as needed for the session.
2) Cleanup the new source tree a lot more, and get it *mostly* compiling (mostly just the backend classes right now - none of the desktop/WM classes yet).
|
| |
|
|
|
| |
Move the system tray registration/management into the XCB Event Filter class itself (since it needs access to the XCB library functions to work). This should restrict almost all use of the XCB classes to the EventFilter instance itself.
Also continue moving around the source files as they are evaluated and tied into the project file. The src-screensaver and src-eventfilter directories are used now, but the src-DE and src-WM directories are still just holding cells for the files from the old lumina-desktop and lumina-wm subprojects that are not yet evaluated.
|
| |
|
|
| |
structures together.
|
|
|
This is just a staging area for the merging of the desktop, window manager, etc.. into a single unified application. It is highly fragmented right now and will not build *AT ALL* for a while.
|
