https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7743
--- Comment #6 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2012-09-23 14:53:19 PDT ---
(In reply to comment #5)
> (In reply to comment #4)
> > That did it, thanks! (I'll leave it to you to commit.)
>
> Great, but do we want to commit/fix it?
> Usually when you write dissector, you group hf[] entries which might be the
> reason of not alphatetical order.
>
> Still in filter expression dialog you can use typeahead feature, just type
> begin of filter name and it will find one for you.
Yes, I think it should be committed. I don't think the order of the hf[]
grouping means much when searching for a filter name.
In my use case, I wanted to filter for "kerberos.msg.type == AS-REP", but I
also wanted to know what other values for kerberos.msg.type were valid, so I
went looking for the filter name to see the list of all predefined values.
Unfortunately, finding kerberos.msg.type was not that easy because the filter
names were not alphabetized.
And now that I think about it, the predefined values should be alphabetized
too.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.