kfm-devel Digest, Vol 148, Issue 10

[Bernard Gray]

> Date: Thu, 23 Jul 2015 19:12:36 +0200
> From: Frank Reininghaus <frank78ac at googlemail.com>
> To: kfm-devel <kfm-devel at kde.org>
> Subject: Re: Dolphin Optical Disk context menu - "Release" function?
> Message-ID:
>         <CAFoZWWib9Cu4kO7kHNcQpy1xc8ODD6a+4K4dKMuXtW8vZWPLJQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
> 2015-07-21 7:57 GMT+02:00 Bernard Gray:
> > ...
> > My question is, what does this Release function do, and how can I execute
> > that release as part of my boot process (ie outside of KDE) so I don't have
> > to pass this non-intuitive step onto my users?
> >
> > I've dived into the dolphin source to try and get a handle on what is
> > happening, but I don't have the Qchops to work out where the slot for that
> > signal gets implemented - hence the question for this list.
>
> I think that the functions
>
> void PlacesItemModel::requestEject(int index)
> void PlacesItemModel::requestTeardown(int index)
>
> are the ones that are run when you safely remove or eject a device.
> However, they are only thin wrappers for functionality that is
> provided by the Solid library, and what this library does in detail
> when these functions are called may depend on the Solid backend that
> is used. I do not know what low-level system calls will be made by the
> backend. Maybe you have to ask the Solid people if noone else on this
> list has an idea.
>
> Regards,
> Frank

Hi Frank,
Thanks very much for the reply - I'll do some more digging with the
new thread you've given me, and get in touch with the Solid guys as
well :)