<br><br><div class="gmail_quote">2009/2/20 Aaron J. Seigo <span dir="ltr"><<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span><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 Friday 20 February 2009, Richard Dale wrote:<br>
> Here because 'if (d->script)' is true, it will call<br>
> showConfigurationInterface on the scripting engine which doesn\'t have the<br>
> KConfigDialog stuff in it.<br>
<br>
</div>KConfigDialog *AppletScript::standardConfigurationDialog()?<br>
<div><div></div></div></blockquote><div>Yes, but how does that differ from just adding createConfigurationInterface() to the scripting api in addition to showConfigurationInterace()?<br><br>As far as I'm concerned showConfigurationInterface() is implemented in Ruby and works just like the C+ version, used with a user written createConfigurationInterface() in Ruby, and so I'm not too bothered about this.<br>
<br>-- Richard<br></div></div><br>