[RFC] Enforcing Compositing

Martin Gräßlin mgraesslin at kde.org
Sun Feb 20 22:40:42 CET 2011

On Sunday 20 February 2011 22:32:47 Davide Bettio wrote:
> Hi,
> On 02/20/11 22:25, Martin Gräßlin wrote:
> > On Sunday 20 February 2011 22:18:16 Davide Bettio wrote:
> >> Hi,
> >> 
> >> On 02/20/11 22:06, Martin Gräßlin wrote:
> >>>> I can't understand the point about removing enable/disable options.
> >>> 
> >>> if we don't want to give the user the possibility to disable, we don't
> >>> need an option to enable/disable.
> >> 
> >> I don't see anything bad about having enable/disable options on the KCM.
> >> The only con that I'm aware of is that we have more checkboxes.
> > 
> > Consider the button would not be there: would you see pro arguments to
> > add one?
> Yes, currently at the computer lab in my university for an unknown
> reason I can't work with compositing enabled, so I had to disable it.
does it have current drivers or is it completely outdated? I am talking about 
at least Mesa 7.10 which is current at the moment and till 4.7 there will be 
Mesa 7.11.
> >> The main reason is that buggy software is still around.
> > 
> > And how do we get the buggy software fixed if we allow workarounds?
> We can't ask users to wait while the software gets fixed, they need to
> work so they may have to disable it while in the meantime someone is
> fixing the bug.
As long as we don't expose the bugs they won't get fixed. What do you think 
would be the state of the drivers if there would not have been the 4.5 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20110220/5d805520/attachment-0001.sig 

More information about the Plasma-devel mailing list