<br><br><div class="gmail_quote">On Wed, May 7, 2008 at 6:52 PM, Ryan P. Bitanga <<a href="mailto:ryan.bitanga@gmail.com">ryan.bitanga@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, May 7, 2008 at 5:48 PM, Ryan P. Bitanga <<a href="mailto:ryan.bitanga@gmail.com">ryan.bitanga@gmail.com</a>> wrote:<br>
> 2008/5/7 Jordi Polo <<a href="mailto:mumismo@gmail.com">mumismo@gmail.com</a>>:<br>
><br>
> ><br>
> > ?<br>
> > Where? AbstractRunner already has the name() method and if you added the<br>
> > reparseConfiguration method I don't know why you need that outside<br>
> > AbstractRunner.<br>
><br>
> I added my own id() method :) You need it outside AbstractRunner bec<br>
> the config dialog is a KCModule. You can't access the runner itself.<br>
><br>
><br>
</div>Let me correct myself. The config widgets for runners are KCModules so<br>
we can use KPluginSelector. KPluginSelector emits the name from<br>
X-KDE-PluginName when a config dialog for a runner is closed. This<br>
matches what is returned by id() and is used for getting the runner<br>
from the RunnerManager. Then I call reparseConfiguration from there.<br>
:)</blockquote><div><br>Ah, ok. I had no idea about how KCModules work and that you where using them. If KDE use whitelist then you completely convinced me. </div></div><br clear="all"><br>-- <br>Jordi Polo Carres<br>NLP laboratory - NAIST<br>
<a href="http://www.bahasara.org">http://www.bahasara.org</a><br>