(Cross-posted to ethereal-dev and ethereal-user)
For "Live" capture & display, if we start out with a static column size and don't resize, we won't be able to view all of the information should a longer line be written to the (for example) Info column. The text storage area may be larger, but the horizontal scroll bar won't take you to the end of the text string unless the column size has been adjusted.
I haven't played with the -S feature yet. I assume that you can select a frame for display, rather than having all of the frames just zoom by without being able to take a closer look. If so, actually seeing the data would be nice.
The other item which is related to this issue is the "Follow-the-Stream" changes. If this is going to put each of the actual application messages on an individual line rather than whatever-sized chunk of data TCP happened to blast out, then I won't be as worried about the full info string. Right now, you wouldn't see some commands, but if each application message gets a display line, then you'd only miss seeing some of the parameters rather than one or more entire messages. Could someone give me a few details on the follow-the-stream implementation?
For the columns other than "Info", the default sizes are probably okay (meaning static width would be okay) during the capture, as they seem to have realistic values for the width.
Regarding user's preference for column type/widths in a .preference file, perhaps we should just have a preference for static or dynamic sizes. Of course, you could do both, having a preference for static or dynamic for each column type, and even a preferred width.
Thanks,
Phil Techau
----------------------------------------------------------------
Get your free email from AltaVista at http://altavista.iname.com
