On Sun, 2006-01-22 at 20:52 +, Neil Williams wrote:
> Only if the other details of the account have changed. How many parameters of
> the account are checked for equality?
Name and placeholder flag.
> Under what circumstances can New Account Hierarchy actually generate a
> conflict?
With
On Sunday 22 January 2006 8:18 pm, Josh Sled wrote:
> On Sun, 2006-01-22 at 19:16 +, Neil Williams wrote:
> Here's a summarization of the situation:
>
> - The new-account-hierarchy druid's revised merge complains and prevents
> the merge if the new account-tree is different than the existing o
On Sun, Jan 22, 2006 at 03:18:36PM -0500, Josh Sled wrote:
> 1/ update the existing account to match the placeholder flag of the
>example account.
>
> 2/ fix the UI so that the placeholder column reflects post-merge
>reality (effectively the current state of the existing account).
>
> 3
[CC'ing gnucash-devel]
On Sun, 2006-01-22 at 19:16 +, Neil Williams wrote:
> I don't understand what's happened to this routine. It was created initially
> to use qof_book_merge but now it picks bad defaults and complains when the
> book already contains accounts - the entire premise of the
