Alien widgets and flickering
robertknight at gmail.com
Tue Mar 18 17:57:40 GMT 2008
> Does anyone object to this patch to systemsettings then?
Please try to make sure there are no unnecessary calls to
QWidget::winId() first. Apart from the screensaver module which you
mentioned, I cannot see why other modules need it.
> and I assume it won't be simple for kwin or style
> kcm's either.
I'm not sure why that would be the case. What does the style KCM need
a winId for?
On 18/03/2008, David Faure <faure at kde.org> wrote:
> On Monday 17 March 2008, Louai Al-Khanji wrote:
> > On Mon, Mar 17, 2008 at 10:51 PM, Alexander Neundorf <neundorf at kde.org> wrote:
> > > On Monday 17 March 2008, Louai Al-Khanji wrote:
> > > > Hi all,
> > > ...
> > >
> > > > The other solution is to throw away the advantages of alien widgets and
> > > > disable them in applications where native widgets are used.
> > >
> > > I have no idea how many applications this are, but if it's only a few, then
> > > this seems like the obvious solution to me.
> > >
> > > Alex
> > >
> > There aren't very many, and I think this is the obviously right choice
> > as well. Does anyone object to this patch to systemsettings then? If
> > not, I will apply it in a few days.
> But the real question IMHO is: why is the winId needed by systemsettings?
> I'm not against the patch, but it should be fully justified, like "systemsettings needs native
> widgets because <xyz>".
> David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
> Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel