[EMAIL PROTECTED] (Bill Gribble) writes:
> On Tue, Nov 28, 2000 at 03:26:47PM +0100, Joerg Schoeppe wrote:
> > I've modified this to:
> >
> > (if (eq? qif-cleared 'cleared)
> > (gnc:split-set-reconcile gnc-near-split #\c))
> >
> > (if (eq? qif-cleared 'reconciled)
> > (g
I'm intending to be away Friday 1st through the morning of Sunday 3rd
December.
--
Robert Merkel [EMAIL PROTECTED]
"We are excited and optimistic about its usage going
forward and, yes, we can teach pengui
James LewisMoss writes:
> Dave> Yes, it seemed to me that 1) (with respect to the GUI) was a
> Dave> part of 2), so it made sense to me to combine them. But perhaps
> Dave> they should be separate things.
>
> I agree. Just seemed the email introduced what was going on as 1 when
> in fact it w
> On Wed, 29 Nov 2000 12:14:00 -0800, Dave Peticolas <[EMAIL PROTECTED]> said:
Dave> This is the introduction of the CM, yes. It is intended to
Dave> manage all major GUI components.
Dave> Close callbacks are commands -- "close yourself now".
OK. It doesn't seem quite like a callback, b
James LewisMoss writes:
>
> Hash table of changes. If gnc_suspend_gui_refresh isn't called the
> refresh callbacks get called for each change?
Yes.
> Dave> The last is used when doing very large amounts of changes, for
> Dave> which it would just be simpler to refresh everything:
>
> Dave
> On Wed, 29 Nov 2000 11:11:33 -0800, Dave Peticolas <[EMAIL PROTECTED]> said:
Dave> James LewisMoss writes:
>> > On Wed, 29 Nov 2000 01:59:22 -0800, Dave Peticolas
>> > <[EMAIL PROTECTED]> sa
>> id:
>>
Dave> Design --
>>
Dave> The refresh mechanism will be designed in two
Derek Atkins writes:
> James LewisMoss <[EMAIL PROTECTED]> writes:
>
> > So a change to data occurs. The engine has a registered listener in
> > the GUI Component Manager that it calls to say something has changed.
> > What happens then?
>
> I suspect that the GUI Component Manager then calls a
James LewisMoss writes:
> > On Wed, 29 Nov 2000 01:59:22 -0800, Dave Peticolas <[EMAIL PROTECTED]> sa
> id:
>
> Dave> Design --
>
> Dave> The refresh mechanism will be designed in two parts, an engine
> Dave> component and a GUI component. The engine component will be a
> Dave> simpl
James LewisMoss <[EMAIL PROTECTED]> writes:
> So a change to data occurs. The engine has a registered listener in
> the GUI Component Manager that it calls to say something has changed.
> What happens then?
I suspect that the GUI Component Manager then calls all the components
that registered a
> On Wed, 29 Nov 2000 01:59:22 -0800, Dave Peticolas <[EMAIL PROTECTED]> said:
Dave> Design --
Dave> The refresh mechanism will be designed in two parts, an engine
Dave> component and a GUI component. The engine component will be a
Dave> simple change callback mechanism, while the GU
The Problem -- Keeping the GUI up to date
-
The GnuCash GUI contains many elements (registers, reconcile windows,
reports, future graphs, main window, etc.) which must be updated when
engine objects (accounts, transactions, splits) are added, deleted or
cha
11 matches
Mail list logo
