>>>>> 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?
(let ((option filename(gnc:expanded-accounts stock expenses expenses:auto))))
??
>> 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
(stocks, expenses, expenses:auto), I think, "why would I _ever_
put something in here?" If we want to allow transactions at that
level, my request should be taken out and shot.
2. What happens with a button2 click on a non-parent? button3 click
on a non-parent already works, so we don't need to add anything
there.
3. adding button2 to expand or close means we can't do anything else
with button2 elsewhere in the account listing.
4. I think that 2x button1 on a parent to expand/close it is the
intuitive way. I probably only think it is intuitive because that
is the way I first thought of it. I hope some other people chime
in with what they want here, or if they don't want anything, to
say that too.
oh, and to top it all off, we all know that if you implement button2
just like you said, my request for this functionality will just wither
until I code it myself, which is just way too funny to even think
about.
ain't open source development models grand? ;-)
rob
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
