>
> >>>>> On Sun, 27 Feb 2000 10:25:13 -0800, Dave Peticolas
> >>>>> <[EMAIL PROTECTED]> said:
>
> Dave> We could have a separate file that is saved in the same
> Dave> directory for each user, but that seems a bit messy. We could
> Dave> save the state in the user's config.auto under a specific file
> Dave> name.
>
> Dave> Anybody have thoughts on this?
> >>
> >> ~/.gnucash/config.auto
> >>
> >> ; Section: Account Types
> >>
> >>
> >> (let ((option (gnc:expanded-accounts stock expenses expenses:auto))))
>
> Dave> That won't work if you use more than one file with different
> Dave> account names.
>
> good point. how are we doing the "register width state" thing for
> different files, same account names, different width choices?
We use the same width throughout. I was thinking that would be less
of a problem, since the width would be similar for different files,
but perhaps we should do that per-file too. Rob's idea of a directory
per account group is starting to make a lot of sense, although that
will require a lot of changes.
> >> did you note that I requested two things there? one of them was
> >> saving state in the account field. the second one was not having
> >> to click on the +- box on a parent account to get it to expand or
> >> shrink.
>
> Dave> How about if using the middle button expanded accounts?
>
> That would be okay, since it would work, but I think it is the wrong
> approach. Here are some reasons why.
>
> 1. Is it a design goal to allow people to open up a parent register
> and actually put transactions in it? I was not thinking that it
> was, and every time I acidentally open up a parent register
Well, there is some disagreement whether or not you should be able
to put transactions in parent accounts. The consensus seems to be
to make it an option. Why don't we just make it user-configurable
whether double-click expands or opens?
dave
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
