https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15775

            Bug ID: 15775
           Summary: Appearance > Font and Colors - no longer allows
                    picking
           Product: Wireshark
           Version: 3.0.1
          Hardware: x86
                OS: Windows 10
            Status: UNCONFIRMED
          Severity: Minor
          Priority: Low
         Component: Common utilities (libwsutil)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: richard_be...@troweprice.com
  Target Milestone: ---

Created attachment 17119
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17119&action=edit
Wireshark Preferences Appearance Font and Colors

Build Information:
Version 3.0.1 (v3.0.1-0-gea351cd8)
--
Prior to version 3.0.1 (such as 2.6.2) the Wireshark Preferences screen for 
   Appearance > Font and Colors
allowed for picking the colors by clicking the colored sample boxes.  A choice
would be presented which you could select what you wanted.
In 3.0.1 I find that there is no action performed and no visible error message.

I verified with a colleague using my PC with 3.0.1 and loading his profiles the
behavior is the same.  Using my userid on his PC Wireshark 2.6.2 behaves well
and I can adjust colors.

My 'spur' to try adjusting the colors was that the 'active selected item' row
doesn't appear with the white text on medium-dark blue background as the
dialogue box shows that it should.  I really want that.  Instead there is a
semi-transparent additional amount of lighter blue.  When selecting a row which
was already light blue, the effect is a little darker. When no color rules are
applied and the list of packets is simply all black text on white background, 
selecting a row results in a medium-light blue for that row with text still
black.

I don't know if the semi-transparent behavior is related to not being able to
select the color appearance of my choice.  Maybe it's a different bug.

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to