Wireshark-bugs: [Wireshark-bugs] [Bug 8269] can't search hex string in the current packet and hi
Comment # 5
on bug 8269
from Evan Huus
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > In general, the Find Packet dialogue could use a redesign for usability
> > > purposes. It's getting a bit confusing as to which options are available
> > > under which type of search.
> >
> > ...something similar to the search bar in the Qt port, perhaps?
>
> It's better than the dialogue, but I'm still not really comfortable with it.
> I'm concerned that if we add more options (like restricting it to the
> current packet) then on narrow monitors there will be no room for the search
> field itself. Also, the fact that the text field is to the right of the
> options feels a bit weird...
>
> My very rough draft of the toolbar would be:
> Search [Display Filters] for: [__________] [Find Next] [Find Previous]
> [Options...] [X]
Another thought: "Packet List", "Packet Details", and "Packet Bytes" shouldn't
be sub-choices of "String", they should just be in the one drop-down. I'm also
not convinced of the utility of searching the packet list (which I assume
searches the displayed columns in the list) since anything searchable there
should be searchable in the packet fields. We might end up with a list like:
"Dissected Data (by field name)"
"Dissected Data (by string)"
"Raw Data (by hex)"
"Raw Data (by string)"
You are receiving this mail because:
- You are watching all bug changes.
