Wireshark-bugs: [Wireshark-bugs] [Bug 2988] Goto undisplayed packet should do something sensible
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2988
--- Comment #2 from Martin Visser <martinvisser99@xxxxxxxxx> 2008-10-27 22:58:55 PDT ---
(In reply to comment #1)
> What do you think would be a better way to handle the "This packet isn't
> displayed..." dialog? Perhaps having buttons on it to go to the next packet
> shown after that packet number or the one before?
>
I had a bit of think about this. The reason why the "click" doesn't match a
displayed packet could be for a couple of reasons
1. You are clicking on a point at time at which there is no packet. The most
obvious thing is to just go the nearest packet. In general this will be good
enough. Also if the zoom level on the graph is such that multiple packets fit
in the tick, just pick the middle one (or first/last). Again I think no warning
is needed. (The user can easily move forward or back a packet)
2. If the display filter for the packet view is different from the graph
display filter, again just pick the nearest packet.
3. If the display filter prevents any packets, just silently ignore the click
In either case for the first time you could just pop up a dialogue "Wireshark
has now selected the nearest packet, this may be long way in time from point on
the graph you have clicked" and allow you the use to tick a checkbox to not
show this message again.
As an aside a great feature would be to be able to click on packet in the
regular window and have the graph scroll to the relevant point in time
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
