Re: [pilot-db-list] More beta 8 buglets

[Scott W. <swa...@my...>]

On Fri, 22 Feb 2002, Mike Ressler wrote:

> On Fri, 22 Feb 2002, Scott Wallace wrote:
> > > 4) The floating type seems to be padded by several spaces on the right
> > > hand side. I.e. when adjusting the view, there is always about 10 pixels
> > > of white space after the 1 decimal place I set. If I attempt to squeeze
> > > the white space, then numbers change to "..." indicating it doesn't fit.
> >
> > Yes, this is true.  There is a 10 pixel margin on the right side of a
> > float column.  If there is no margin, what happens is that the float is
> > directly adjacent to the value in the next column (since most columns are
> > left justified) ...
> > you could make the margin disappear as the the column becomes increasingly
> > full.  But this requires calculating the max width overall columns, which
> > is too slow.  So instead, I just use a constant value.
> 
> Is it that slow? I guess the real question is how often the value would
> have to be recalculated. If it can be calculated only when the DB is
> opened, it should be tolerable. (You may then have to close and reopen the
> database to get it to update correctly.) I would think that calculating
> the maximum width of one of the elements, right justifying each element
> within this box width, then _left_ justifying boxes within the column
> based on the width given in the list view would be the best way to attack
> this.

Yes, you could calculate the value when opening and then update it each 
time a record was added, deleted or removed, but currently, there is no 
support to do such a thing, and it would mean a fairly significant 
internal change, that I would rather avoid now that we are so close to 
release.

In the meantime I'll lower the padding from 10 to 4 pixels...

	-Scott