am really starting to hate Plasma::ScrollWidget - that widget is
resizing on timer so to not cause resizing to minimum and then expanding
manual widget resizing has to be done (see
Plasma::WidgetExplorerPrivate::filterApplets())
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
CheckBox, RadioButon and Slider are actually registed by graphicswidgets
(there are Plasma::CheckBox, Plasma::RadioButton and Plasma::Slider
classes for such widgets), Switch is simply unused
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
lots of references have to be kept and passed around because once the
device is removed Solid::Device is just an UDI - anything else is
obtained dynamically and will return invalid results (even casts will
not work)
what the mountpoint cleaner does? when a device is removed without
being unmounted (e.g. USB storage) the program will call `unmount`
essentially making sure the device node and the mount point can be used
when the device is inserted again, no other project does that as far as
I am aware
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
can implement condition for when device changes occurs too but I have no
plans to use it for something, not yet that is. the remove condition can
(and probably will be) used to start kvkbd when there is no keyboard
plugged in altough that will require program to check when to do that
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
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>
Plasma::Applet::init() and Plasma::Applet::constraintsEvent() may be called
in order such that the members were not created yet
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
side note: the places runner may also add matches for the removable devices
because the places implementation handles them as bookmarks (the devices
in the dolphin places panel are bookmarks!
see kdelibs/kfile/kfileplacesitem.cpp)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
using solid directly and not depending on soliduiserver for the actions,
now the hotplug and devicenotifications data engines aswell as the
devicenotifier applet can be reimplemented too
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>
