|author||Havoc Pennington <firstname.lastname@example.org>||2002-01-27 05:50:34 +0000|
|committer||Havoc Pennington <email@example.com>||2002-01-27 05:50:34 +0000|
make the check for whether to eat focus click a lot more complicated
2002-01-27 Havoc Pennington <firstname.lastname@example.org> * src/display.c (event_callback): make the check for whether to eat focus click a lot more complicated * src/window.c (meta_window_same_application): new function * src/prefs.h, src/prefs.c: add application based pref * src/metacity.schemas: add "application_based" setting to give me a mode to fool with being application based, without being unusable in the meantime. Yeah the crack flows freely these days. Everyone knew it would happen.
Diffstat (limited to 'src/metacity.schemas')
1 files changed, 26 insertions, 0 deletions
diff --git a/src/metacity.schemas b/src/metacity.schemas
index 355a909..4f6fb4b 100644
@@ -116,6 +116,32 @@
+ <locale name="C">
+ <short>Navigation works in terms of applications not windows</short>
+ If true, then Metacity works in terms of applications rather
+ than windows. The concept is a bit abstract, but
+ in general an application-based setup is more like
+ the Mac and less like Windows. When you focus a window
+ in application-based mode, all the windows in the
+ application will be raised. Also, in application-based
+ mode, focus clicks are not passed through to windows
+ in other applications.
+ The existence of this setting is somewhat questionable.
+ But it's better than having settings for all the specific
+ details of application-based vs. window-based, e.g.
+ whether to pass through clicks. Also, application-based mode
+ is largely unimplemented at the moment.