how does it look? something like this:
https://ibb.co/1zbDVpk
and because all the SolidUiServer bits are written by me now - copyright
it to me. the actions dialog was not operational btw (not for hotplug
events anyway).
the solidautoeject thing does not even make sense - when the eject
button is pressed it was calling Solid::OpticalDrive::eject() but if the
button is pressed the tray will eject anyway so what was it doing
actually?
solid-device-automounter can be replaced with solid actions but the
devices are mounted for solid actions anyway so dropping it
as for KCM for the solid actions - there can be none but to add features
such as non-interactive actions (e.g. launch the keyboard KCM when a
keyboard is plugged without poping dialog) or actions that do something
on device removal it has to be done anew
note that the action file for opening a file manager was named
"test-predicate-openinwindow" meaning it was a testing thing rather than
a finished thing
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
lots of changes with this commit - on the plasma applet side:
+ the applet now handles mouse wheel events
* the applet itself sets its global global shortcut key
+ the applet itself has configuration interface for the text and flag options
* ported to the new KKeyboardLayout class
- no per-window or per-application keyboard layout
on the overall keyboard configuration:
* no KDED module required
+ keyboard layout descriptions (model, layout, variant, etc.) are actually translated
- no keyboard configuration will be shown when a keyboard is plugged-in (see bellow)
- keyboard layout options are not configurable, not via GUI interface anyway
the hotplug plasma data engine, device notifications and solid actions
have to be either reimplemented or extended to handle more device types
(currently the above mentioned handle only removable devices by default
such as cameras, not input devices such as keyboard)
overall - from reimplemented one thing to another and the keyboard
configuration is not done yet (adding and editing keyboard layout not
implemented yet) but in a working state
on a side note the changes here affect kvkbd as it uses D-Bus interface
for keyboard layout change that is no more and has to be ported or (most
likely) replaced with a handler for QEvent::RequestSoftwareInputPanel
event that shows a keyboard on demand
there is also the double-keyboard layout applet thing - applet for the
keyboard layout could be added and the daemon (KDED module) was showing
its own keyboard layout indicator automatically (by default)
the X11 keyboard bell options are next to useless btw - there is
KNotification::beep() for such things so the X11 bell options are
simply dropped
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the only use case is to launch ksnapshot which can be done by
plasma-desktop, some of the actions code is borked (notably window
matching, global and menu actions were working) and I have no
intention to fix it. even if fixed when a window (and thus possibly
application) key is grabbed there is a chance the window (application)
may want to grab the grabbed key and fail (i.e. grab conflict) so it
shall be left to the application to set what keys shall be global
(grabbed) hence the bits to start ksnapshot are moved to plasma-desktop
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
see the following commit in kdelibs repo:
4b632fcae67da3b95e69e954fa2e581a42f4c53c
currently enabled only for a few applications until more tests are done
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
on a side note generating backtrace via drkonqi was not working on some
systems where traces are disabled by default (for security reasons) and
it required not only to install debug packages or build for debugging
purposes but also to setup the system so that backtrace can be generated
to get something out of it
where that is no the case on Linux there is usually a core dump in the
system log anyway thus the only thing a program related to crashes has
to do is to notify about it and (when possible) automatically file some
information (with the option to disable that)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
one of the things that the previous implementation was lacking is the
credentials handling, also it was was very slow because it had to spawn
a process
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
also corrected folderview applet condition in olderView::setUrl()
(incorrect since before the fork, was displaying message that the
network is not reachable when the status is connected)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
able to watch any mounted device, not just the home directory. bonus
points for configuration interface that does not show up only when the
device used to store the home directory is low on space
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
by the time ksplash gets the X11 events for startup phases the startup
process is (and should be) done, especially after the display
configuration is done and the monitor is ready to output thus ksplash
does not really indicate much
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
no image handler for EXR now and the thumbnail may be too small to fit
well in the file properties dialog, if there is image handler (plugin)
for EXR the generic image thumbnailer can still create one
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
I cannot think of a use case for them with kdirshare service in place,
never needed to access one either
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
