[Kmymoney-devel] restoring QWidget::updatesEnabled property

[Alvaro Soliverez]

On Mon, Jul 27, 2009 at 3:52 AM, Cristian Oneţ <onet.cristian at gmail.com>wrote:

> În data de Luni 27 Iulie 2009 04:05:38 Alvaro Soliverez a scris:
> > On Sun, Jul 26, 2009 at 11:11 AM, Cristian Oneţ
> <onet.cristian at gmail.com>wrote:
> > > În data de Duminică 26 Iulie 2009 16:06:27 Alvaro Soliverez a scris:
> > > > > It is enough to explicitly enable the updates but I would prefer
> > > > > disabling/restoring the updates in the transaction form only if
> that
> > > > > is needed
> > > > > (when they are not already disabled). That way when the updates on
> > > > > the parent
> > > > > widget are re-enabled they will also be re-enabled on the
> transaction
> > > > > form.
> > > >
> > > > Can you emit a signal and connect it to a slot that will
> > >
> > > setUpdatesEnabled
> > >
> > > > to true?
> > > > That might do it.
> > >
> > > What do you say about the attached patch instead of setting up a
> signal?
> > >
> > > Well, it's simpler than setting up a signal.  :))
> >
> > Does updatesEnabled return false only if it is disabled explicitly or
> > always when a parent widget has been disabled?
> It returns false when updates are disabled on a parent (that was the
> initial
> problem that we restored this "false" value and the framework acted like we
> disabled the updates explicitly)
>
> > Do you think this will catch all cases?
> I think it is the best compromise between wanting to disable updates and
> restore their original state after disabling but nonetheless avoid an
> explicit
> disabling by doing this.
>
>
Commit it, then, and let's see how this approach works.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kmymoney-devel/attachments/20090727/3af4b7e5/attachment.htm