Report system legacy

Christian Stimming christian at
Fri Jun 28 16:22:25 EDT 2013

Am Donnerstag, 27. Juni 2013, 07:18:14 schrieb John Ralls:
> On Jun 27, 2013, at 7:04 AM, Derek Atkins <warlord at MIT.EDU> wrote:
> > Geert Janssens <janssens-geert at> writes:
> >>> HOWEVER, I do think that we should only have a single saved report
> >>> of
> >>> the same name. I.e., if we save a Balance Sheet report it goes into
> >>> Custom/Balance Sheet which is fine. But if you *resave* it, IMHO it
> >>> should overwrite the previously saved Custom report of the same
> >>> name.
> >> 
> >> That may not be the user's real intention. Instead the user may want
> >> to
> >> generate a second report based on the same base report, but using
> >> different settings. So I think automatically overwriting the
> >> previously saved report may result in user frustration. At the very
> >> least we should ask the user what she wants to do.
> > 
> > I'm not sure..  Perhaps the best way to do it would be to do it similar
> > to other systems and prompt the user: "Another saved report already
> > exists with the name XXX.  Overwrite?  [Cancel] [OK]" This would prompt
> > them to change the name if they really want two reports with the same
> > name.
> Alternatively, do what Macs do: append ' (n)' to the name part of the
> filename, where n is a positive integer incremented as necessary.

I think we shouldn't add any suffix to the report name automatically. I also 
think we shouldn't have multiple saved reports with the same name. To resolve 
this, I think Derek's proposal works best: Saving the report requires a unique 
name among the saved custom reports (but which might be identical to the non-
custom report). If the report with this name already exists as custom report, 
the user gets a question "Another report already exists with the name XX. 
Overwrite? [Cancel] [Ok]" and no additional options. If the user doesn't want 
to overwrite, he/she always can guess to "Cancel" here and then change the 
name to have it unique again.



More information about the gnucash-devel mailing list