| From: Biot Olivier
|
| | From: Richard Sharpe
| |
| | On Tue, 30 Dec 2003, Ulf Lamping wrote:
| |
| | > >I am not sure how this plays with the other options. Could
| | it be better
| | > >handled by a radio button that says Save displayed packets?
| | > >
| | > You mean, like the print dialog, I have done some time ago?
| |
| | OK, it really looks like the "... but displayed packets
| only" really
| | applies to a number of the choices above, so it probably should be:
| |
| | [] Save only displayed packets
| |
| | However, since people really expect the displayed packets to
| | be saved, and
| | might not be aware that there are filtered packets that are
| | in the capture
| | but not displayed, perhaps we should say:
| |
| | [] Also save any packets not currently displayed
|
| To me this is confusing in the way that I (along with many
| other Ethereal
| users in their novice time) believed that "displayed" meant
| "visible in the
| UI" hence limiting the scope to the number of visible
| GtkCList rows in the
| "packet view" widget, which it isn't. I think it is more
| intuitive to talk
| about a filter always being used by default instead of packets being
| displayed or not as the latter allows more than one
| interpretation. But then
| we probably should take more time in introducing the filters
| in the manual
| :)
I would keep the "Save As" widget as is, but refer to the active dfilter in
the tooltip, as in: "Only consider packets from the packet range above which
also match the current display filter expression". Should we then label the
check box with "Restrict the range to the currently displayed packets"?
The tooltip for manual packet range selection does not show an example.
Otherwise I'm really *Very* Fond of the new widget!
Regards,
Olivier