--------------3B3C18AF2951B0E817D795EB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Conrad Canterford wrote:
> Dave Peticolas wrote:
> > James LewisMoss writes:
> > > Dave> What should happen when the register is resized smaller?
> > > I don't know for sure. All I'm sure about is the current behavior is
> > > annoying. :)
> <trimmed>
> > When the window is resized larger, the 'description' field is enlarged
> > to take up slack if the resulting register would be smaller than the
> > window (to avoid an annoying white bar at the right edge).
> > When the window is resized smaller, no columns are adjusted, since
> > there is no danger of having the extra white space.
> > However, this does create an asymmetry between enlarging and reducing
> > the window size.
> > What if we reduced the 'description' field when the window is reduced,
> > but only if the register exactly fits the window?
>
> I realise it is much more work, but wouldn't it be better to increase
> each column proportionally in either direction? Remember the changes
> that the user makes, and when they resize the entire window, keep each
> column the same percentage of window width before the resize as after.
> This is what I expected on gut instinct the first time I used Gnucash.
> Took me a while to figure the strange behaviour out (this was back on
> 1.3.???).
>
> Conrad.
> --
> Conrad Canterford (conrad@mail.watersprite.com.au)
> Water Sprite Pty Ltd | info@mail.watersprite.com.au
> GPO Box 355, | Incorporating:
> Canberra, ACT, 2601 | Australian Tour and Event Management (ATEM)
> Australia. | Ticketing Services Division
> Phone: 0419 122 553 | Catering Services Division
The behavior of the 1.4.X series seems quite adequate to me. It increases
or decreases the 'description' field and leaves the other fields fixed. The
width of the data in most of the other fields is nearly constant anyway.
--
Gilligan | __o .oooO
/| _ \<,_ ( )
/p|\ (_)/ (_) \ ( Oooo.
/ | \ ------------ \_) ( )
======== ) /
======== gilligan@mpinet.net (_/
~~~~~~~~~~~~~~~~ uschold@cs.ucf.edu
--------------3B3C18AF2951B0E817D795EB
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
Conrad Canterford wrote:
Dave Peticolas wrote:
> James LewisMoss writes:
> > Dave> What should happen when the register is resized smaller?
> > I don't know for sure. All I'm sure about is the current
behavior is
> > annoying. :)
<trimmed>
> When the window is resized larger, the 'description' field is enlarged
> to take up slack if the resulting register would be smaller than
the
> window (to avoid an annoying white bar at the right edge).
> When the window is resized smaller, no columns are adjusted, since
> there is no danger of having the extra white space.
> However, this does create an asymmetry between enlarging and reducing
> the window size.
> What if we reduced the 'description' field when the window is reduced,
> but only if the register exactly fits the window?
I realise it is much more work, but wouldn't it be better to increase
each column proportionally in either direction? Remember the changes
that the user makes, and when they resize the entire window, keep each
column the same percentage of window width before the resize as after.
This is what I expected on gut instinct the first time I used Gnucash.
Took me a while to figure the strange behaviour out (this was back
on
1.3.???).
Conrad.
--
Conrad Canterford (conrad@mail.watersprite.com.au)
Water Sprite Pty Ltd | info@mail.watersprite.com.au
GPO Box 355,
| Incorporating:
Canberra, ACT, 2601 | Australian Tour
and Event Management (ATEM)
Australia.
| Ticketing Services Division
Phone: 0419 122 553 | Catering Services
Division
The behavior of the 1.4.X series seems quite adequate to me. It increases
or decreases the 'description' field and leaves the other fields fixed.
The width of the data in most of the other fields is nearly constant anyway.
--
Gilligan | __o .oooO
/| _ \<,_ ( )
/p|\ (_)/ (_) \ ( Oooo.
/ | \ ------------ \_) ( )
======== ) /
======== gilligan@mpinet.net (_/
~~~~~~~~~~~~~~~~ uschold@cs.ucf.edu