| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
| |
start testing and see if windows respond to the EWMH hints.
|
| |
|
|
| |
class.
|
| |
|
|
| |
NativeWindowSystem (GlobalPos, Size, MinSize, MaxSize)
|
| |
|
|
| |
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.
|
| |
|
|
| |
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.
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
| |
This reduces the number of widgets in the stack by 1, and seems to help performance a bit.
|
| |
|
|
| |
a possible c++11 build warning/error.
|
| | |
|
| | |
|
| | |
|
|
|
Now the utilites are arranged by category (core, core-utils, desktop-utils), so all the -utils may be excluded by a package system (or turned into separate packages) as needed.
|
