Re: Byte view mouse hover behaviour

[Roland Knall <rknall () gmail com>]

Looks to me that we actually have an inconsistency in behavior. If you
click on a byte, the underlying field gets selected in the byteview as well
as packetdetail pane and stays selected, until you click someplace else. If
you do the same the other way around, it does not work, as the selection is
not locked in in the byteview.

Bugfix inbound, and I don't think it needs to be configurable, as it
actually solves the underlying issue

cheers
Roland

Am Sa., 11. Sept. 2021 um 15:45 Uhr schrieb John Thacker <
johnthacker () gmail com>:

> On Sat, Sep 11, 2021 at 7:23 AM Jaap Keuter <jaap.keuter () xs4all nl> wrote:
>
> > Hi all,
> >
> > Often when working with captured data from some development setup I
> > wonder around the packet bytes with the mouse pointer to try and follow
> > where in the code under development certain parts of a packet contents is
> > being created. What happens now is that the highlighting of the field where
> > this particular bytes are from follows the mouse pointer. But I'm working
> > the other way around, by first selecting a field in the packet details,
> > then dive into the packet bytes, where I would like the selected field
> > highlighting to remain, so I can navigate around while keeping my bearings
> > in the packet.
> >
> > But I recon this will upset people. So putting it behind a preference
> > would a the way to go. The the question becomes where to put that? Anyone a
> > good idea?
>
> I would appreciate that, I have wished for that behavior myself. While one
> option is just giving it a name so that people can only access it through
> Preferences->Advanced, I think the most natural place is in
> Appearance->Layout. There's already a section for Packet List settings
> there, that includes a preference for "Enable mouse-over colorization." (
> https://gitlab.com/wireshark/wireshark/-/blob/master/epan/prefs.c#L3377-L3380)
> Perhaps add a "Packet Bytes settings" group and then the new preference.
>
> Cheers,
> John Thacker
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe