Bug 594897 - gui window very difficult to read
Summary: gui window very difficult to read
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: report
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Gavin Romig-Koch
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 594895
Blocks: 594898
TreeView+ depends on / blocked
 
Reported: 2010-05-21 21:31 UTC by Gavin Romig-Koch
Modified: 2010-11-10 21:29 UTC (History)
5 users (show)

Fixed In Version: report-0.16-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 594895
: 594898 (view as bug list)
Environment:
Last Closed: 2010-11-10 21:29:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gavin Romig-Koch 2010-05-21 21:31:48 UTC
+++ This bug was initially created as a clone of Bug #594895 +++

The GTK GUI window that asks "Where would you like to send this report?" is very difficult to read.  It displays a row of buttons horizontally which, if there is lots of buttons, will stretch across the screen, and could stretch off the screen.

A better way would be to display the buttons vertically.

Also, the title in the window manager bar above the window is just "Query", haveing it repeat the question "Where would ..." would be better.

Comment 2 RHEL Program Management 2010-06-07 16:09:31 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Gavin Romig-Koch 2010-06-17 17:39:35 UTC
Pushed to fedorahosted src repo/master branch.

Comment 7 releng-rhel@redhat.com 2010-11-10 21:29:25 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.