> Lastly, some comments.. When selecting the follow tcp stream, a magic filter
> rule appears in the "filter window" and the display window pops up. May I
> suggest that the display window have its own "filter" window?
The display window isn't a packet display, so I'm not sure what its
filter window would do.
The filter rule in the filter window is a rule to limit the display to
the packets in the TCP connection in question; said limitation is
entirely intentional, as it provides a convenient way to look at the
packets in a TCP connection.
> That would
> eliminate quite a bit of hassle that happens when following one stream, and
> then having to put the original filter rule back in and locate the next packet
> to do a follow stream on.
Note that the filter box is a combo box, and that the drop-down list
should include all filters other than the ones inserted for "Follow TCP
Stream", so that if the original filter rule isn't one generated by
"Follow TCP Stream", it should be possible to put it back by selecting
it from the drop-down list.
If the problem is that you don't want the display filtered when you do
"Follow TCP Stream", then we need to have two operations on TCP streams,
one of which collects the stream data into a "Follow TCP Stream" window
but doesn't filter the display, and one that filters the display and
*perhaps* also pops up a "Follow TCP Stream" window - or perhaps
doesn't, as one could get that window by selecting any packet in the
display and then doing "Follow TCP Stream".
