Browsing Malay translation

21.

metacity %s
Copyright (C) 2001-2002 Havoc Pennington, Red Hat, Inc., and others
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

70.

A font description string describing a font for window titlebars. The size from the description will only be used if the titlebar_font_size option is set to 0, however. Also, this option is disabled if the titlebar_uses_desktop_font option is set to true. By default, titlebar_font is unset, causing Metacity to fall back to the desktop font even if titlebar_uses_desktop_font is false.

74.

Arrangement of buttons on the titlebar. The value should be a string, such as "menu:minimize,maximize,close"; the colon separates the left corner of the window from the right corner, and the button names are comma-separated. Duplicate buttons are not allowed. Unknown button names are silently ignored so that buttons can be added in future metacity versions without breaking older versions.

76.

Clicking a window while holding down this modifier key will move the window (left click), resize the window (middle click), or show the window menu (right click). Modifier is expressed as "<Alt>" or "<Super>" for example.

86.

If true, and the focus mode is either "sloppy" or "mouse" then the focused window will be automatically raised after a delay (the delay is specified by the auto_raise_delay key). This preference is poorly named, but kept for backwards compatibility. To try to be more clear (at least to the technically inclined), its meaning is "automatically raise the window following a timeout which is triggered by non-grabbed mouse entry in sloppy or mouse focus modes". It is unrelated to clicking behavior (i.e. this is not related to raise-on-click/orthogonal-raise). It is unrelated to entering a window during drag and drop (because that results in the application grabbing the mouse)

88.

If true, metacity will give the user less feedback and less sense of "direct manipulation", by using wireframes, avoiding animations, or other means. This is a significant reduction in usability for many users, but may allow legacy applications and terminal servers to function when they would otherwise be impractical. However, the wireframe feature is disabled when accessibility is on to avoid weird desktop breakages.

89.

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.

92.

Many actions (e.g. clicking in the client area, moving or resizing the window) normally raise the window as a side-effect. Set this option to false to decouple raising from other user interactions. When false, windows can still be raised by an alt-left-click anywhere on the window or a normal click on the window decorations (assuming such clicks aren't used to start a move or resize operation). Special messages, such as activation requests from pagers, may also raise windows when this option is false. This option is currently disabled in click-to-focus mode.

132.

Show the panel run application dialog

133.

Some applications break specifications in ways that result in window manager misfeatures. For example, ideally Metacity would place all dialogs in a consistent position with respect to their parent window. This requires ignoring application-specified positions for dialogs. But some versions of Java/Swing mark their popup menus as dialogs, so Metacity has to disable dialog positioning to allow menus to work in broken Java applications. There are several other examples like this. This option puts Metacity in full-on Correct mode, which perhaps gives a moderately nicer UI if you don't need to run any broken apps. Sadly, workarounds must be enabled by default; the real world is an ugly place. Some of the workarounds are workarounds for limitations in the specifications themselves, so sometimes a bug in no-workarounds mode won't be fixable without amending a spec.