On Fri, 2006-08-12 at 23:10 -0500, Derek Atkins wrote:
Quoting Phil Longstaff [EMAIL PROTECTED]:
The main difference is the root.. SXes all live in their own AccountGroup,
separate from the CoA. Why do you need anything special? Why can't you
load the SXes too?
I can. I need to
I've included a portion of the GDA_STATUS file which brings up some
questions:
- To avoid having the backend commit everything twice (because of the
Qof two phase commit protocol), saved objects are marked clean when
committed. To do this, I need to reach right into the QofInstance
structure and
On Fri, 2006-12-08 at 17:34 -0500, Phil Longstaff wrote:
I'm working on saving/restoring scheduled transactions, and have some
questions:
1) Accounts - The only difference I can see between regular accounts and
the accounts created for scheduled transactions is in the currency - the
Quoting Phil Longstaff [EMAIL PROTECTED]:
- To avoid having the backend commit everything twice (because of the
Qof two phase commit protocol), saved objects are marked clean when
committed. To do this, I need to reach right into the QofInstance
structure and clear the dirty flag. There
On Sat, Dec 09, 2006 at 11:53:52AM -0500, Phil Longstaff wrote:
I've included a portion of the GDA_STATUS file which brings up some
questions:
- Recurrences are currently only used by budgets, and recurrence
save/restore is included in the budget save/restore code. If
recurrences will
On Sat, 2006-09-12 at 13:19 -0500, Derek Atkins wrote:
Quoting Phil Longstaff [EMAIL PROTECTED]:
- To avoid having the backend commit everything twice (because of the
Qof two phase commit protocol), saved objects are marked clean when
committed. To do this, I need to reach right into the
Quoting Phil Longstaff [EMAIL PROTECTED]:
On Sat, 2006-09-12 at 13:19 -0500, Derek Atkins wrote:
Quoting Phil Longstaff [EMAIL PROTECTED]:
- To avoid having the backend commit everything twice (because of the
Qof two phase commit protocol), saved objects are marked clean when
committed.
Phil Longstaff wrote:
Yes. Fixed in r15194.
Phil
Trying another build.
Are you using--enable-compile-warnings? At the moment, I am leaving it out.
Mark
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
On Sat, 2006-09-12 at 15:13 -0700, Mark Johnson wrote:
Phil Longstaff wrote:
Yes. Fixed in r15194.
Phil
Trying another build.
Are you using--enable-compile-warnings? At the moment, I am leaving it out.
I'm not. Maybe I'll turn it on.
Phil
Quoting Phil Longstaff [EMAIL PROTECTED]:
Are you using--enable-compile-warnings? At the moment, I am leaving it out.
I'm not. Maybe I'll turn it on.
Yeah, you should configure with --enable-error-on-warning
--enable-compile-warnings --enable-debug ... The latter is
probably optional, but
On Sat, 2006-09-12 at 17:40 -0500, Derek Atkins wrote:
Quoting Phil Longstaff [EMAIL PROTECTED]:
Are you using--enable-compile-warnings? At the moment, I am leaving it
out.
I'm not. Maybe I'll turn it on.
Yeah, you should configure with --enable-error-on-warning
Quoting Phil Longstaff [EMAIL PROTECTED]:
- Recurrences are currently only used by budgets, and recurrence
save/restore is included in the budget save/restore code. If
recurrences will eventually be used elsewhere in GC, recurrence
save/restore code may need to be split out on its
On Sat, Dec 09, 2006 at 06:37:55PM -0500, Derek Atkins wrote:
Quoting Phil Longstaff [EMAIL PROTECTED]:
- Recurrences are currently only used by budgets, and recurrence
save/restore is included in the budget save/restore code. If
recurrences will eventually be used elsewhere in GC,
The thing about FreqSpec is that they don't look like they need to be
evenly spaced. I don't know why you would not do that, but you might
want a FreqSpec to be last friday of every month or 15th and 30th of
every month which Recurrence wouldn't handle.
Sure it could. Recurrence
Phil Longstaff wrote:
On Sat, 2006-09-12 at 17:40 -0500, Derek Atkins wrote:
Quoting Phil Longstaff [EMAIL PROTECTED]:
Are you using--enable-compile-warnings? At the moment, I am leaving it out.
I'm not. Maybe I'll turn it on.
Yeah, you should configure with
Quoting Chris Shoemaker [EMAIL PROTECTED]:
The thing about FreqSpec is that they don't look like they need to be
evenly spaced. I don't know why you would not do that, but you might
want a FreqSpec to be last friday of every month or 15th and 30th of
every month which Recurrence
16 matches
Mail list logo