returns the state set by the user - these two may differ e.g. while hover-unshaded.
Therefore titlebar buttons should use isSetShade(), otherwise they become
a bit useless with hover-unshading.
Also fix updating the button state - the styles duplicate way too much code,
and if one of them has a bug, most of them definitely have it as well. Some
of the code should probably move to the decoration lib :-/ .
svn path=/trunk/kdebase/kwin/; revision=366147
(The user visible strings inkdebase/kwin/clients are extracted to
kwin_client.pot)
CCMAIL:kde-i18n-doc@kde.org
svn path=/trunk/kdebase/kwin/; revision=347824
Add a central user message extraction for all KWin client.
(The config programs have already their own .pot files)
CCMAIL:kde-i18n-doc@kde.org
(Note: there is currently not much of a choice to add a new .pot file,
as KWin has already many of them and we are in message freeze.
But at least this new .pot file can be shared between all clients, which
share most of the user visible strings.)
svn path=/trunk/kdebase/kwin/; revision=332022
first time and until this problem can be clearer.
Reason: from my first test, there are mostly the same strings ("Maximize",
"Minimize"...) and therefore such mini-pot files full of duplicates
should not be created. (That the config files are even extra files is bad too.)
svn path=/trunk/kdebase/kwin/; revision=331821
Of course, this will multifold break compile as well as a dozen of people
will now object that they actually wanted the Id tags.
svn path=/trunk/kdebase/ksysguard/; revision=290873
The current implementation does not offer the largest two sizes as for those the buttons need to be scaled (which requires bigger changes as the buttons are based on pixmaps).
svn path=/trunk/kdebase/kwin/; revision=254093
Since Qt propagates mouse events up the widget hierarchy, it's better
to filter out Qt events rather than X events for the decoration.
svn path=/trunk/kdebase/kwin/; revision=252346
clients by adding an unnecessary 'enable-bidi' checkbox which was never agreed
upon on the kwin mailing list.
The use of --reverse is sufficient without needing this checkbox.
Please discuss largish patches like these first, especially during a feature
freeze!
(Everyone also seems to forget the kwin-styles in kdeartwork)
- Make clients look the same with --reverse instead of the broken state they
were in previously. If the button ordering is not to your liking in reverse
mode, just change the button positions. (Or send patches for those clients
that have not got these features yet).
- Clean up popupMenu handling somewhat.
- Remove a global static object in keramik.
svn path=/trunk/kdebase/kwin/; revision=174079
if it's on, kwin clients will reverse thire display when the desktop is reversed (arabic, hebrew etc).
Clinets updated to use this options, and options.h has a few more lines :)
see clients for the changes.
svn path=/trunk/kdebase/kwin/; revision=173581
his part of the patch, works fine but there's just the re-check needed to
be added so when the effect for tooltips changes, the deco's tooltips take
this as well. There are no new strings except the Un-Sticky tooltip, all
others are translated. thd@kde.org agreed on the strings.
svn path=/trunk/kdebase/kwin/; revision=104585
The patch allows the modsystem handle to be shown / hidden, and
adds a config plugin for kwindecoration where this can be configured.
svn path=/trunk/kdebase/kwin/; revision=93544
init() called after client got loaded
deinit() called when client is about to get unloaded
reset() called once before Options::resetClients() is emitted
svn path=/trunk/kdebase/kwin/; revision=93372
visible dialogs for stays-on-top fullscreen windows (helps with Konqueror's dialogs)
Fixed lock with Alt-Tab box plus accelerator
svn path=/trunk/kdebase/kwin/; revision=65241
now only has one button entry, "ButtonBg", instead of 3. It's up to the client
what to do with it. All the clients are updated except mwm. As the
author noted in his README, mwm isn't Motif window manager at all but KStep ;-)
I disabled it for now until there is new drawing code in there, it would
confuse users anyways since were about to release another Krash and it is
identical to KStep.
Also, I removed the Groove and GrooveText color entries. We now use the
normal TitleBar and Font entries. Hence system will probably look funny until
you adjust the colors since it draws text on the frame and not the titlebar
bg. All the rest look much better by default.
To configure button colors set the active/inactive button background color
in KControl. I'll remove the other entries ASAP. You'll also note that the
active/inactive colors are now actually what you would expect.
svn path=/trunk/kdebase/kwin/; revision=47753
from the KStyle aqua theme - color reduced, converted to bitmaps, and drawn
using the color scheme. The buttons in different color schemes shows why it's
really cool to support dynamic C++ engines as well as pixmap themes ;-) Also
uses a small frame with a resize handle and mac-like (hehe - of course ;-)
drawing for everything else.
Preliminary screenshots with different color schemes are at:
http://www.mosfet.org/modern-0428.html
svn path=/trunk/kdebase/kwin/; revision=47624
