Ethereal-users: Re: [ethereal-users] Column Widths with -S on 0.6.3

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Scharf <guy@xxxxxxxxx>
Date: Tue, 20 Jul 1999 06:31:42 -0700
Guy Harris wrote:
> 
> > > Well, it's not working well!  Each time the display updates -- even if
> > > no data in the currently visible set of records changes, the column
> > > widths change.  The go wide, then pop back to the original narrow
> > > settings (cutting off most data), then go wide again.
> >
> > I.e., they do all three of those in sequence?
> >
> > If so, then the fact that it cuts off most data is only a minor glitch,
> > as the widths go back to normal.
> >
> > I can't reproduce that, and can't see a way in which the code would
> > produce that behavior;
> 
> OK, I've seen that one after I've backed out a change I recently checked
> in; without that change, before reading in the newly-captured packets,
> it reset its notion of the column sizes to the sizes of the column
> titles, so that the column widths it chose would take into account only
> the most recent set of packets it read, so it could shrink the columns.
> 
> With my change, however, it doesn't do that.

That describes the situation.  The "narrow" columns do seem to fit the
column titles well.  Then it pops back to a width that holds all.  Then
it shrinks to title-width columns again.

I still don't like the idea of resizing columns each time new records
are read with -S.  If I am trying to examine some of the packets
captured so far without stopping the capture process, I don't want the
screen flickering and changing on me.  That makes it very hard to
examine the data.

Guy