<br><br><div class="gmail_quote">On Sun, Jul 26, 2009 at 11:11 AM, Cristian Oneţ <span dir="ltr"><<a href="mailto:onet.cristian@gmail.com">onet.cristian@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
În data de Duminică 26 Iulie 2009 16:06:27 Alvaro Soliverez a scris:<br>
<div class="im">> > It is enough to explicitly enable the updates but I would prefer<br>
> > disabling/restoring the updates in the transaction form only if that is<br>
> > needed<br>
> > (when they are not already disabled). That way when the updates on the<br>
> > parent<br>
> > widget are re-enabled they will also be re-enabled on the transaction<br>
> > form.<br>
><br>
> Can you emit a signal and connect it to a slot that will setUpdatesEnabled<br>
> to true?<br>
> That might do it.<br>
</div>What do you say about the attached patch instead of setting up a signal?<br>
<br>
</blockquote><div>Well, it's simpler than setting up a signal. :))<br><br>Does updatesEnabled return false only if it is disabled explicitly or always when a parent widget has been disabled?<br>Do you think this will catch all cases?<br>
<br>Regards,<br>Alvaro<br></div></div><br><br>