No double-buffering for decorations, the memory taken
by such backing pixmaps would be quite noticeable. svn path=/branches/work/kwin_composite/; revision=632377
This commit is contained in:
parent
bb5f7a9519
commit
1397ebb5eb
1 changed files with 3 additions and 4 deletions
|
@ -62,6 +62,7 @@ void KDecoration::createMainWidget( Qt::WFlags flags )
|
|||
// FRAME check flags?
|
||||
QWidget *w = new QWidget( initialParentWidget(), initialWFlags() | flags );
|
||||
w->setObjectName("decoration widget");
|
||||
w->setAttribute( Qt::WA_PaintOnScreen );
|
||||
setMainWidget(w);
|
||||
}
|
||||
|
||||
|
@ -395,9 +396,7 @@ const QPalette& KDecorationOptions::palette(ColorType type, bool active) const
|
|||
int idx = type + (active ? 0 : NUM_COLORS);
|
||||
if(d->pal[idx])
|
||||
return(*d->pal[idx]);
|
||||
#ifdef __GNUC__
|
||||
#warning KDE4 : why construct the palette this way?
|
||||
#endif
|
||||
// TODO: Is this worth 'porting' to Qt4?
|
||||
// d->pal[idx] = new QPalette(Qt::black, d->colors[idx], d->colors[idx].light(150),
|
||||
// d->colors[idx].dark(), d->colors[idx].dark(120),
|
||||
|
@ -447,7 +446,7 @@ KDecorationDefines::WindowOperation KDecorationOptions::operationMaxButtonClick(
|
|||
button == Qt::MidButton? d->OpMaxButtonMiddleClick :
|
||||
d->OpMaxButtonLeftClick;
|
||||
}
|
||||
#ifdef __GNUC__
|
||||
|
||||
#warning Redo all the XYZChange() virtuals as signals.
|
||||
#endif
|
||||
|
||||
#include "kdecoration.moc"
|
||||
|
|
Loading…
Reference in a new issue