Browsing Slovak translation

341.

This option determines the effects of middle-clicking on the title bar. Current valid options are 'toggle-shade', which will shade/unshade the window, 'toggle-maximize' which will maximize/unmaximize the window, 'toggle-maximize-horizontally' and 'toggle-maximize-vertically' which will maximize/unmaximize the window in that direction only, 'minimize' which will minimize the window, 'shade' which will roll the window up, 'menu' which will display the window menu, 'lower' which will put the window behind all the others, and 'none' which will not do anything.

343.

This option determines the effects of right-clicking on the title bar. Current valid options are 'toggle-shade', which will shade/unshade the window, 'toggle-maximize' which will maximize/unmaximize the window, 'toggle-maximize-horizontally' and 'toggle-maximize-vertically' which will maximize/unmaximize the window in that direction only, 'minimize' which will minimize the window, 'shade' which will roll the window up, 'menu' which will display the window menu, 'lower' which will put the window behind all the others, and 'none' which will not do anything.

345.

If set to true, and the focus mode is either "sloppy" or "mouse" then the focused window will be automatically raised after a delay specified by the auto-raise-delay key. This is not related to clicking on a window to raise it, nor to entering a window during drag-and-drop.

361.

Tells the WM how to implement the visual indication that the system bell or another application 'bell' indicator has been rung. Currently there are two valid values, "fullscreen-flash", which causes a fullscreen white-black flash, and "frame-flash" which causes the titlebar of the application which sent the bell signal to flash. If the application which sent the bell is unknown (as is usually the case for the default "system beep"), the currently focused window's titlebar is flashed.

362.

(Not implemented) Navigation works in terms of applications not windows

363.

If true, then the WM 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. Application-based mode is, however, largely unimplemented at the moment.

371.

Select the proxy configuration mode. Supported values are "none", "manual", "auto". If this is "none", then proxies are not used. If it is "auto", the autoconfiguration URL described by the "autoconfig-url" key is used. If it is "manual", then the proxies described by "/system/proxy/http", "/system/proxy/https", "/system/proxy/ftp" and "/system/proxy/socks" will be used. Each of the 4 proxy types is enabled if its "host" key is non-empty and its "port" key is non-0. If an http proxy is configured, but an https proxy is not, then the http proxy is also used for https. If a SOCKS proxy is configured, it is used for all protocols, except that the http, https, and ftp proxy settings override it for those protocols only.

373.

URL that provides proxy configuration values. When mode is "auto", this URL is used to look up proxy information for all protocols.

384.

If true, then connections to the proxy server require authentication. The username/password combo is defined by "/system/proxy/http/authentication-user" and "/system/proxy/http/authentication-password". This applies only to the http proxy; when using a separate https proxy, there is currently no way to specify that it should use authentication.