brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

updated description of raise_on_click:

Browse Source 
* src/metacity.schemas.in.in: updated description of
	  raise_on_click:
	  http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6


svn path=/trunk/; revision=4016
This commit is contained in:
Thomas James Alexander Thurman 2008-11-10 12:51:33 +00:00
parent 203046237c
commit d079ef538c
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -1,3 +1,9 @@
2008-11-10 Elijah Newren <newren gmail com>
* src/metacity.schemas.in.in: updated description of
raise_on_click:
http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6
2008-11-08 Thomas Thurman <tthurman@gnome.org>
* configure.in: added dependency on Zenity

19
src/metacity.schemas.in.in
View File

@ -90,11 +90,30 @@
<short>Whether raising should be a side-effect of other user
interactions</short>
<long>
Setting this option to false can lead to buggy behavior, so
users are strongly discouraged from changing it from the default
of true.
Many actions (e.g. clicking in the client area, moving or resizing the window)
normally raise the window as a side-effect. Setting this option to false, which
is strongly discouraged, will decouple raising from other user actions, and
ignore raise requests generated by applications. See
http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6.
Even when this option is false, windows can
still be raised by an alt-left-click anywhere on the window, a
normal click on the window decorations, or by special messages
from pagers, such as activation requests from tasklist applets.
This option is currently disabled in click-to-focus mode.
Note that the list of ways to raise windows when raise_on_click
is false does not include programmatic requests from
applications to raise windows; such requests will be ignored
regardless of the reason for the request. If you are an
application developer and have a user complaining that your
application does not work with this setting disabled, tell them
it is _their_ fault for breaking their window manager and that
they need to change this option back to true or live with the
"bug" they requested.
</long>
</locale>
</schema>