blob: c2c1e74da932f7bafa5982228591b8c69cf4a8e2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
CONTENTS:
=========
1. Pre-configuring window-specific settings
1. Pre-configuring window-specific settings
===========================================
Window-specific settings is a feature of KWin that allows specifying some
settings only for a specific window or windows. See the Window-specific
settings section in the KWin configuration and the Special settings
menu entries in Alt+F3/Advanced menu.
One aspect of window-specific settings is the ability to specify various
workarounds for (usually broken) applications that otherwise don't work
properly with KWin. This section describes how to create additional
window-specific settings that will be automatically used by all users
without any need of manual configuration.
Example case:
Application FooBar does not specify any maximum size for its main window,
but when resized to larger size than 1600x1200 it crashes because of a bug.
Manual configuration of a window-specific setting that avoids this problem
is opening and activating this window, selecting
Alt+F3/Advanced/Special window settings, activating tab Workarounds, enabling
setting Maximum size, changing it to Force and entering "1600,1200" as
the maximum size, which will make KWin force this size as the maximum size.
To create such window-specific setting automatically without a need of doing
it manually for every user (for example when doing a large deployment), follow
these steps:
- Back up your $KDEHOME/share/config/twinrulesrc ($KDEHOME usually being $HOME/.kde)
and remove it
- Run 'dcop twin default reconfigure'
- Create manually all window-specific settings that should be included (see above)
- When done, check in Window-specific settings configuration module
(Alt+F3/Configure window behavior/Window-specific settings) that all rules are
included
- Create a copy of $KDEHOME/share/config/twinrulesrc and restore the original one
- Rename the copy (i.e. the newly created twinrulesrc) to have its unique name
(e.g. foobar_fix_maxsize in this example case)
- Be careful with manual modifications of the file, especially make sure the count=
field in the [General] group is updated if needed
- Create a file for kconfig_update like this (named twin_foobar_fix_maxsize.upd
in this example):
# twin_foobar_fix_maxsize.upd start #
Id=foobar_fix_maxsize
File=twinrules_update
Group=Dummy
Options=overwrite
ScriptArguments=foobar_fix_maxsize
Script=twin_update_default_rules
# twin_foobar_fix_maxsize.upd end #
- The kconfig_file (twin_foobar_fix_maxsize.upd) is to be placed
in $KDEDIR/share/apps/kconf_update/
- The file with the window-specific settings (foobar_fix_maxsize) is to be placed
in $KDEDIR/share/apps/twin/default_rules/
All KDE user accounts should have these new window-specific settings added
automatically during next KDE startup (or within few seconds if they are active).
They can be checked again in the Window-specific settings configuration module of KWin.
|
