Bug 530263 - Allow configuring new windows to be always placed on top
Summary: Allow configuring new windows to be always placed on top
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: metacity
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Owen Taylor
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
: 476237 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-22 03:26 UTC by Owen Taylor
Modified: 2018-10-27 14:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 08:26:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch implementing described option (7.81 KB, patch)
2009-10-22 03:26 UTC, Owen Taylor
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0245 0 normal SHIPPED_LIVE metacity bug fix and enhancement update 2010-03-29 12:44:04 UTC

Description Owen Taylor 2009-10-22 03:26:02 UTC
Created attachment 365645 [details]
Patch implementing described option

When a new window is denied focus (for example, because it is a
notification window that has an older timestamp than the last user
interaction) the current behavior is that it would otherwise overlap
the focus window it is stacked under the focus window and flashed
in the taskbar. On a small screen like a laptop this works well,
however if the user has a large screen or multiple monitors, then
mousing to the taskbar is inconvenient, and the user may not see the
flashing taskbar at all (since it isn't in their peripheral vision.)

This patch adds a GConf key:

 /apps/metacity/general/new_windows_always_on_top

Described as:

  The normal behavior is that if a new window is not given the
  focus (since, for example, the user has interacted with another
  window after launching an application), then if the window would
  be stacked on top of the focus window, the window is instead
  stacked beneath and flashed in the taskbar. This behavior can
  be annoying on large screens and multihead setups where the
  taskbar is hard to notice and difficult to get to, so this option,
  if set, disables this behavior, and new windows are always placed
  on top, whether or not they get focus.

  Note that if this option is set, a new window may completely hide
  the focus window but not get focus itself, which can be quite confusing
  to users. Also, note that setting this option breaks the normal
  invariant in the 'click' focus mode that the topmost window always
  has focus, so its most suitable for use with the 'mouse' and
  'sloppy' focus modes.

Upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=599261

To test:

1) Set focus mode to sloppy:

 gconftool-2 -t string -s /apps/metacity/general/focus_mode sloppy 

2) Configure gnome-keybinding-properties to not get the focus:

 gconftool-2 -t string -s /apps/metacity/general/no_focus_windows \
  '(eq class "Gnome-keybinding-properties")'

3) run 'gnome-keybinding-properties' from the command line and verify
  that it does not get the focus; it will be stacked under the
  window and flashed in the taskbar.

4) Configure new windows to be stacked on top:

 gconftool-2 -t boolean -s /apps/metacity/general/new_windows_alway_on_top true

5) Run 'gnome-keybindings-properties' again and check that it is now
   stacked on top of the terminal (but still does not get the focus)

Comment 1 Owen Taylor 2009-11-11 20:58:22 UTC
built in dist-5E-qu-candidate as metacity-2.16.0-15.el5

Comment 2 Owen Taylor 2009-12-08 20:28:33 UTC
*** Bug 476237 has been marked as a duplicate of this bug. ***

Comment 9 errata-xmlrpc 2010-03-30 08:26:02 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0245.html


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