There is a comment in the code to say that the crosshairs with the lines didn't work well with cairo. The code is still there but things are currently configured to use the crosshair cursor instead.
I have reused the TCP graph code for another protocol recently, and plan to try enabling the line-drawing code to see if I can see what goes wrong. An alternative might be a text control that gets updated with time+sequence number when the cursor moves. Does anyone know what went wrong with the cross-hair lines, or on what platforms?
Martin
On Wed, Aug 1, 2012 at 4:29 PM, Dana J. Dawson
<Dana.Dawson@xxxxxxxxxxxxxxx> wrote:
So I'm guessing not many people use this feature (assuming it really is a feature). I've also noticed that the crosshairs have become a small "+" symbol instead of the vertical and horizontal hairlines that extended all the way to both axes, which made it easier to determine the values of the associated coordinates for the crosshair location. It would be nice if that old behavior returned as well.
Should I be submitting a bug report/feature request for this stuff?
Thanks!
Dana
On Jul 5, 2012, at 4:53 PM, Dana J. Dawson <Dana.Dawson@xxxxxxxxxxxxxxx> wrote:
> I use the various TCP Graphs quite a bit and just noticed that scrolling a zoomed TCP Graph, such as a Time Sequence graph, by clicking and dragging with the right mouse button no longer seems to work with the new 1.8.0 version. I've tried this both on Windows 7 and Mac OS X Lion and get the same behavior. Falling back to 1.6.8 restores the feature. I haven't found this panning feature documented in any of the Wireshark manuals, so maybe this is not a supported feature, but if it is expected to work it no longer seems to.
>
> Has anyone else encountered this yet? I know I can use the arrow keys, but the resolution is a bit coarse via that method and it's much less convenient.
>
> Thanks in advance!
>
> Dana
___________________________________________________________________________
Sent via: Wireshark-users mailing list <
wireshark-users@xxxxxxxxxxxxx>
Archives:
http://www.wireshark.org/lists/wireshark-users
Unsubscribe:
https://wireshark.org/mailman/options/wireshark-users
mailto:
wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
