[Alexis La Goutte <alexis.lagoutte@xxxxxxxxx>]

On Wed, Jan 17, 2018 at 1:39 PM, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote:

-----Original Message-----
From: Wireshark-dev [mailto:wireshark-dev-bounces@wireshark.org] On Behalf Of Gerald Combs
Sent: den 17 januari 2018 02:05
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] 2.5.0 release on January 16

On 1/13/18 4:16 AM, Stig Bjørlykke wrote:
> We still have some regression issues after 2.5 refactoring which
> should be fixed.
> Does anyone work on this?
>
>
> Qt/UI regression issues after refactoring:
> - Qt: Missing string translations after source code was moved to
> utils/models/manager/widgets subdirectories
> - Qt: Plurality does not work for strings in
> utils/models/manager/widgets files

Do you know what's missing? This shouldn't be too hard to fix.

> - PacketList: Markers in "Number" columns are gone
> - PacketDetails: Only top-level node-expansion is remembered when
> switching between packets
> - PacketDetails: Link colours in links are gone

The last couple of updates to proto_tree.cpp should fix these.

> - ByteView: Wrong font size on startup and profile change (if using
> other size than default)

Not sure what's causing this.

> - ByteView: Hovering bytes does not highlight the field as it used to
> do
> - ByteView: Vertical white and horisontal black lines issues
> - ByteView: Color issue when clicking a byte multiple times

The 2.4 byte view didn't distinguish between hovered and a locked bytes. I initially tried to do so by drawing an overline+undlerline over hovered bytes and coloring locked bytes. Change 25348 draws a full outline instead of an overline+undlerline.

I think this bug needs attention too...
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14317

+1 it is a blocking issue...

Regards
Anders

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
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@xxxxxxxxxxxxx>
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