|
17.
|
|
|
<h1>Window-specific Settings</h1> Here you can customize window settings specifically only for some windows. <p>Please note that this configuration will not take effect if you do not use KWin as your window manager. If you do use a different window manager, please refer to its documentation for how to customize window behavior.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
kcm.cpp:81
|
|
34.
|
|
|
For selecting all windows belonging to a specific application, selecting only window class should usually work.
|
|
|
i18n: file detectwidgetbase.ui line 179
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:34
|
|
35.
|
|
|
Use window class and window &role (specific window)
|
|
|
i18n: file detectwidgetbase.ui line 187
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:37
|
|
36.
|
|
|
For selecting a specific window in an application, both window class and window role should be selected. Window class will determine the application, and window role the specific window in the application; many applications do not provide useful window roles though.
|
|
|
i18n: file detectwidgetbase.ui line 190
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:40
|
|
38.
|
|
|
With some (non-KDE) applications whole window class can be sufficient for selecting a specific window in an application, as they set whole window class to contain both application and window role.
|
|
|
i18n: file detectwidgetbase.ui line 201
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:46
|
|
40.
|
|
|
A single shortcut can be easily assigned or cleared using the two buttons. Only shortcuts with modifiers can be used.<p>
It is possible to have several possible shortcuts, and the first available shortcut will be used. The shortcuts are specified using space-separated shortcut sets. One set is specified as <i>base</i>+(<i>list</i>), where base are modifiers and list is a list of keys.<br>
For example "<b>Shift+Alt+(123) Shift+Ctrl+(ABC)</b>" will first try <b>Shift+Alt+1</b>, then others with <b>Shift+Ctrl+C</b> as the last one.
|
|
|
i18n: file editshortcutbase.ui line 26
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:52
|
|
98.
|
|
|
I&nactive opacity in %
|
|
|
i18n: file ruleswidgetbase.ui line 1862
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:614
|
|
115.
|
|
|
Strictly obey geometry
|
|
|
i18n: file ruleswidgetbase.ui line 2293
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:775
|
|
117.
|
|
|
Enable this checkbox to alter this window property for the specified window(s).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
ruleswidget.cpp:55
|
|
118.
|
|
|
Specify how the window property should be affected:<ul><li><em>Do Not Affect:</em> The window property will not be affected and therefore the default handling for it will be used. Specifying this will block more generic window settings from taking effect.</li><li><em>Apply Initially:</em> The window property will be only set to the given value after the window is created. No further changes will be affected.</li><li><em>Remember:</em> The value of the window property will be remembered and every time time the window is created, the last remembered value will be applied.</li><li><em>Force:</em> The window property will be always forced to the given value.</li><li><em>Apply Now:</em> The window property will be set to the given value immediately and will not be affected later (this action will be deleted afterwards).</li><li><em>Force temporarily:</em> The window property will be forced to the given value until it is hidden (this action will be deleted after the window is hidden).</li></ul>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
ruleswidget.cpp:57
|