Neil Williams <[EMAIL PROTECTED]> writes:
> 3. I propose leaving the initial call to gncBookMerge as requiring that both
> books be explicitly specified, import and target.
> There is no intrinsic need (except memory / performance) for gncBookMerge to
> be restricted to only merging into the currently active book - it is possible
> to specify two other books and merge those without affecting the active book.
> The purpose of such a merge is up for debate but it might be useful.
> :-) Is this agreeable?
Yes, you should use explicit books.
> 5. The outline of the dialog control procedure is now working - it's
> implemented as a callback for each rule that needs user intervention. There's
> an Init() call with the two QofBook pointers, the callback over each compared
> rule and a Commit() operation. If anyone has some time to work on the GUI
> code, I would be very grateful. My testing will continue in console mode for
> now - would this be at all useful in the final code, to be able to pass two
> GnuCash files and output a merged file with the same collision handling, all
> on the command line?
I think it would be useful... At least for testing.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
