<br><br><div class="gmail_quote">On Sun, Jul 26, 2009 at 10:00 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 15:53:56 Alvaro Soliverez a scris:<br>
<div><div></div><div class="h5">> On Sun, Jul 26, 2009 at 8:45 AM, Cristian Oneţ<br>
<<a href="mailto:onet.cristian@gmail.com">onet.cristian@gmail.com</a>>wrote:<br>
> > În data de Sîmbătă 25 Iulie 2009 15:10:03 Alvaro Soliverez a scris:<br>
> > > On Sat, Jul 25, 2009 at 5:38 AM, Cristian Oneţ<br>
> ><br>
> > <<a href="mailto:onet.cristian@gmail.com">onet.cristian@gmail.com</a>>wrote:<br>
> > > > În data de Sîmbătă 25 Iulie 2009 11:15:55 ați scris:<br>
> > > > > În data de Sîmbătă 25 Iulie 2009 10:01:12 ați scris:<br>
> > > > > This is why I think that trying to restore the flag does not work<br>
> > > > > for the transaction form unless we have some call to explicitly<br>
> > > > > enable<br>
> ><br>
> > the<br>
> ><br>
> > > > updates<br>
> > > ><br>
> > > > > like we do for the register.<br>
> > > ><br>
> > > > Or we could do the disable/restore stuff only if we really need it,<br>
> ><br>
> > that<br>
> ><br>
> > > > is,<br>
> > > > when updates are not already disabled when reaching that code.<br>
> > ><br>
> > > I can't remember which class it was right now, but I remember there was<br>
> > > a point in the code where it would call setEnabled for each tab. It was<br>
> > > commented out and added #warning #Port to KDE4.<br>
> ><br>
> > Do you mean the setEnabled call from TabBar::copyTabs? That code has been<br>
> > ported and it does not help with this issue. But I think that the fact<br>
> > that a<br>
> > widget is enabled/disabled and the fact that the updates for the widget<br>
> > are enabled/disabled are unrelated.<br>
> ><br>
> > My mistake. It's been a while since I have looked at that code.<br>
><br>
> Perhaps the Qt3 code relied on the fact that the transaction form would be<br>
> enabled anyway even if explicitly disabling the updates, but in Qt4 that<br>
> has to be done by hand.<br>
><br>
> Is it enough to just enable the updates explicitly or another widget is<br>
> being disabled in addition to the transaction form?<br>
</div></div>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 needed<br>
(when they are not already disabled). That way when the updates on the parent<br>
widget are re-enabled they will also be re-enabled on the transaction form.<br>
<br>
</blockquote></div><br>Can you emit a signal and connect it to a slot that will setUpdatesEnabled to true?<br>That might do it.<br>