| Commit message (Collapse) | Author | Age |
|
|
|
| |
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.
|
|
|
|
|
|
| |
lumina-open call now, instead of a bunch of individual ones). Also fix up the tray app detection/failover methods a bit to catch/discard tray icons which were registered/destroyed almost simultaneously (or no destroy event was ever caught for the icon). This prevents the situation where a "blank" tray icon may be trying to repaint itself repeatedly (eating up CPU cycles).
NOTE: It seems like these "blank" tray apps are all GTK based, so it might be something in that toolkit which needs fixing to prevent registering a tray window which will never be used (or is instantly destroyed).
|
|
|
|
|
|
|
|
| |
1) Add a new ResizeMenu() class to the LuminaUtils library - this class allows the resulting menu to be resizable by the user clicking on an edge and dragging.
2) In the systemstart panel plugin, reverse the location of the shutdown options on the leave page (put them at the bottom next to where the leave button is in the first place)
3) Setup the systemstart plugin to use the new ResizeMenu. It currently does not save the new size to be used for later sessions, but per-session resizing works fine.
4) Quick adjustment to the systemtray icon sizes
5) Quick fix to the detection of a desktop file removal.
|
|
|
|
| |
Also turn off some debuging information from the system tray plugin.
|
|
|
|
| |
panels "detecting" when the mouse leaves the window.
|
|
|
|
| |
Found out that (at least on FreeBSD 10.2 right now), the xcb_damage_create() routine does absolutely nothing (no damage events ever sent out when the window changes). Switching this back to the Xlib XDamageCreate() routine makes it work perfectly again. Need to ask about this upstream and see if this is a known bug/regression in the XCB libraries.
|
|
|
|
| |
This plugins is an overall "start" menu for the system, combining the functionality of the userbutton and the system dashboard into a single unified interface.
|
|
|
|
| |
functions in lumina-desktop.
|
|
|
|
| |
off the debugging for the session/desktop/panel classes by default.
|
|
|
|
| |
creation to XCB, and place it within the embedding routine in LuminaX11 instead.
|
|
|
|
| |
tinker with the session cleanup routine quite a bit to streamline the order in which things are closed down (particularly with system tray apps).
|
|
|
|
| |
the XCB->WindowImage() function which was just removed.
|
|
|
|
| |
of XLib. This bahaves exactly the same on my FreeBSD 10.x system - still need to test a FreeBSD 11.x system.
|
|
|
|
| |
was moved into QScreen)
|
| |
|
|
|
|
| |
for non-valid *.desktop files.
|
|
|
|
|
|
|
| |
(system tray) to use the new routine.
Also setup the desktop to use the new XCB routine for window icons as well.
Both are tested on 10.x and appear to work perfectly.
|
|
|
|
|
|
| |
will be aware of the new status change (send an event instead of changing the property directly).
Also add a quick fix for system tray icons: if the icon size does not match the tray size, send a resize event and redraw a few moments later.
|
|
|
|
| |
It is functional at the moment, but still has a few rough edges with regards to the X11 background interface (due to the move from XLib to XCB in Qt5). This reulst in some of the window manager interactions not behaving properly (such as sticky status on panels).
|
|
|
|
|
|
|
| |
1) Now the Lumina session registeres the system-wide tray, and just keeps track of the windows that should be visible (preventing any loss of service or apps starting up before the tray is registered).
2) The system tray plugin is now just a "visual tray" for embedding the applications in the panel. The Session only allows a single visual tray to be registered at a time, but sends out signals whenever there is an opening for a visual tray (allowing near-instant transfer of tray applications from one visual tray to another).
Also fix a quick bug in lumina-config where the save button was getting activated simply by changing the appearance/plugins tab in the panel configuration (without actually changing anything).
|
|
|