Hi Miklos, <br><br>Keep us posted on your progress.<br><br>Thanks<br>Jc<br><br><div class="gmail_quote">On Fri, Nov 25, 2011 at 10:52 AM, Miklos Espak <span dir="ltr"><<a href="mailto:espakm@gmail.com">espakm@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Fri, Nov 25, 2011 at 3:58 PM, Julien Finet <<a href="mailto:julien.finet@kitware.com">julien.finet@kitware.com</a>> wrote:<br>
> Hi Miklos,<br>
><br>
> Looking at the code, it seems that the signal is fired:<br>
><br>
> //-----------------------------------------------------------------------------<br>
> void ctkWorkflowWidgetStepPrivate::createUserInterfaceCompleteInternal()const<br>
> {<br>
> emit createUserInterfaceComplete();<br>
> }<br>
><br>
> It is done in the Pimpl though. If you search for<br>
> "createUserInterfaceComplete" in CTK, you'll find some use case.<br>
> To be honest, I've no idea how it works :-)<br>
> Maybe Jc or Danielle can comment on it.<br>
><br>
> I am surprised you need to listen for createUserInterfaceComplete, I<br>
> would expect to do all the initialization work in<br>
> ctkWorkflowWidgetStep::createUserInterface().<br>
<br>
</div>I have to fill the input widgets with values when I arrive at a<br>
workflow step. I would do it in the onEntry, but at the first onEntry<br>
call the user interface is not ready.<br>
<br>
So I have to check in the onEntry if the GUI is created or not. This<br>
cannot be queried by the ctkWorkflowStepWidget functions.<br>
<br>
But no problem, I rearrange my code so I can decide it by a null check.<br>
<br>
Best,<br>
<font color="#888888">Miklos<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>+1 919 869 8849<br><br>