<br><br><div class="gmail_quote">2008/3/11 Kevin Ottens <<a href="mailto:ervin@kde.org">ervin@kde.org</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Le Sunday 09 March 2008, Marco Martin a écrit :<br>
<div class="Ih2E3d">> but i am stuck in an ugly series of problems, i wanted to write about it<br>
> when i had some useful code, but i really don't know how to make it work :(<br>
> i wanted to put the eject icon only on mounted devices, so i have to watch<br>
> the mount status of the device, i suppose it could be done with the<br>
> soliddevice dataengine i suppose, if i understood correctly, giving it a<br>
> query with an udi like connectSource(udi, this); it would return the info<br>
> for the device with that udi, but it doesn't seem to work, i'm missing<br>
> something or there are problems in that engine?<br>
><br>
> is the right way to do it with soliddevice engine? or should be used solid<br>
> directly?<br>
<br>
</div>Well, since you'll have to act on the device I'd say use solid directly, you<br>
already have all the info you need from the hotplug engine to do it. In this<br>
particular case I doubt the soliddevice engine will have an added value... As<br>
your patch shows you're forced to use the relevant Solid classes anyway. In<br>
your case it just adds complexity I'm afraid.<br>
<br></blockquote></div><br>However once Plasma::Service is implemented a Service will be provided that will allow him to do these things alleviating him from having to access Solid directly. Also, isn't this the point of the whole dataengine/applet paradigm? That applets don't have to access frameworks directly? Otherwise devicenotifier could just access Solid::Notifer directly too.<br>
<br>Chris<br>