When you have filtered frames using a display filter, "Mark All" will mark all
the displayed items. You can then use a different diplay filter to match some
other packets, mark them and so on. Then you can save all the marked frames
without having to use a super-complex display filter to match all the frames
you want.
So, yes... it is used :-)
However, when the focus is on the input widget for entering a filter, it might
be nicer to have it bound to the same text editing function as you have in
emacs. You could file an enhancement request for having the text editing
options available in the filter input widget.
Cheers,
Sake
----- Original Message -----
From: yami
To: Developer support list for Wireshark
Sent: Sunday, March 22, 2009 10:16 AM
Subject: Re: [Wireshark-dev] Is 'mark all packets' functionality widely
used(or is it useful?)?
I see. Thanks!
Of course we can mark the excluded ones and save 'unmarked packets' for this
scenario, however I feel 'saving unmarked' is not intuitive for end users.
On Sun, Mar 22, 2009 at 3:51 PM, Stephen Fisher <[email protected]>
wrote:
On Sun, Mar 22, 2009 at 03:08:05PM +0800, yami wrote:
> I can not figure out why marking all packets is a useful
> functionality. Could anyone kindly give some use cases?
You can mark all packets, then unmark certain ones before saving.
Steve
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
------------------------------------------------------------------------------
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
