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>
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>
much like prior to f47177f876 except that
the notification is not done on solid signals but from the KDED module
responsible for mounting and unmounting
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
