| Commit message (Collapse) | Author | Age |
|
|
|
| |
coordinate system. Also setup the desktop plugins to assign a default size for themselves in grid-space rather than pixels (better accounts for screen scaling and such on high-resolution monitors).
|
|
|
|
| |
fix an issue with the calendar plugin not scaling down appropriately on the bottom/right edges.
|
|
|
|
|
|
|
| |
1) Adjust the font outlines quite a bit more - now it properly respects the theme settings and adjusts appropriately.
2) Add options to re-size all the desktop icons at the same time (use 16 pixel increments)
3) Adjust the default desktop icon size (use a 64x64 icon be default).
4) Ensure that the applauncher re-scales the icon as necessary to ensure it is the proper size.
|
|
|
|
|
|
| |
1) Make sure the calendar desktop plugin updates the date occasionally.
2) Add the framework for a custom-painted Toolbutton for the applauncher plugin. This will be used to ensure font outlines in the near future.
3) Another small adjustment for new window geometries - run the overall adjustment first - then re-check and see if the window is off the top of the screen before trying the fallback movement routine.
|
|
|
|
|
|
|
|
|
| |
- Now the desktop plugins are drag-and-drop based, resulting in the user being able to simply drag the plugins around as necessry.
- All the plugins now have a special context menu (right-click, or click and hold the left mouse button for 1/2 second), which provides options to start moving/resizing the plugin as well as the removal option.
Known Issues:
- The cross-application drop event for files is currently flagged as valid - but does not actually run anything yet (to be finished up soon)
- Hidden panels are not being updated when plugins are moved around yet - resulting in some screen artifacting on the panel. (to be fixed soon)
|
|
|
|
| |
routines may be added (only used for some applaunchers right now). This now makes a desktop icon which was explicitly closed/removed by the user also delete the file from the desktop folder (instead of having that plugin get re-created at a later time)
|
| |
|
|
|
|
| |
created/arranged initially. Now the desktopview should be oriented the proper way, and the applauncher icons should be the proper size (although they are still not being placed in non-overlapping locations yet).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
watchers:
1) Move the ~/Desktop directory watcher into the Session (no extra overhead, already have a watcher there), and have te session send out signals when the contents of the ~/Desktop dir change.
2) Setup the plugins that poll the desktop to use the new session implementation (reducing overhead overall)
3) Add the ability to use files/dirs in the "applauncher" plugin as well (not exposed to user yet)
4) Add a new desktop flag for auto-creating applauncher plugins for any files/dirs on the desktop (not added to lumina-config yet)
5) Get rid of all the config files for the desktop plugins and merge them all together into a single conf file that the session maintains the pointer to (so plugins can grab that pointer as necessary)
6) Make sure that desktop plugins go through a special [read/save]Setting() functions in the plugin implementation itself so that they don't accidentally trample other plugin settings (keeps it restricted to the particular group for that plugin)
|
|
|
|
| |
initialization. Something about the addition processEvents() call is screwing up the init procedures.
|
| |
|
|
|
|
| |
desktop plugin widgets by the name of the plugin. Leaving this disabled by default until some more testing is performed to see how well it works.
|
|
|
|
|
|
|
|
| |
1) Desktop plugins are not getting removed.
- This appears to be a bug in Qt 5.4.1 from what I can tell (any window buttons in the QMdiSubWindow are non-responsive), but for the moment the user can right-click on the plugin titlebar and select "close" from the menu for the same effect. I have fixed a couple edge cases/situations where forcibly closing/removing a desktop plugin will crash the session (it behaves properly in all situations now from my testing).
2) Disable the panel location limitations in lumina-config since with the new lenght settings it is possible to place panels in any location now (such as two panels on the top - one pinned left and the other pinned right).
3) Fix up the desktop plugin area calculations so they properly handle panels in any configuration.
4) If the desktop area was re-configured, go through and adjust the location/sizing of any desktop plugins (to ensure that they are all within the available space - use the grid alignment procedure).
|
|
|
|
| |
active window and then re-activate that other window when the mouse leaves the panel.
|
|
|
|
|
|
|
|
|
| |
to the desktopview plugin:
1) Multi-item selection
2) cut/copy files to clipboard
3) delete files
4) increase/decrease icon sizes
|
|
|
|
| |
transparent/opaque on a plugin-level. This allows for finer control via the theme.
|
|
|
|
|
| |
1) Now the panel appearance will be set by the theme as well (unless custom appearance set)
2) Now the desktop plugins are themed appropriately as well (background canvas can be set to something, non-transparent plugins can be changed)
|
|
|
|
| |
This plugin provides an area of the screen for automatically displaying icons for anything in the ~/Desktop folder. An icon can be opened/run via a double-click of the mouse.
|
|
|