Heath Martin <[EMAIL PROTECTED]> writes:
> This is exactly what I want. So, the top line could be given a
> "percentage of space" specification like (0.2, 0.1, 0.5,0.01,...)
> [something that adds to one] and the other row like
> (0.1, 0.1, ... ). This would make some columns line up correctly (e.g., the
> right sides of the date field on the top line, and the number field on
> the second line). We could also specify left/right borders, etc. or
> whatever.
This sounds a lot like the HTML/XML/(La)TeX table layout problem...
> This is probably possible, but I'm not sure how to do it the right
> way. I haven't looked at any of the startup files, but I believe it
> wouldn't be difficult to support. Isn't it mainly a GUI thing
> anyway? The GUI, given enough hints, can either ignore or enhance
> what the table and splitreg provide, as long as the data it needs is
> in the table.
Right.
> (Another example: what to do about the enter key?)
IMO, enter and return should mean "record transaction and move to
next", and tab should mean complete field (if you're in a
tab-completion field and the completion's not unique) and move to next
field otherwise. In cases where tab-completion is ambiguous
i.e. between "Foobar Savings" and "Foobar Savings extra", the right
arrow would be your escape.
At least I think that's what I think I'd be most comfortable with...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
