Extreme display corruption

[Nikos Chantziaras]

On 09/14/2009 03:41 PM, Andreas Pakulat wrote:
> On 14.09.09 15:26:52, Nikos Chantziaras wrote:
>> On 09/14/2009 02:20 PM, Milian Wolff wrote:
>>> Nikos Chantziaras, 14.09.2009:
>>> What happens if you start another application with the `--graphicssystem
>>> raster` parameter - does that also mess up things?
>>
>> Yes.  So I guess KDE default is to *not* use raster.  I think it's a bad
>> idea for KDevelop to not follow whatever is the default on the user's
>> system.
>
> The default is Qt's choice, not KDE's.

Doesn't really matter as long as it's a default.


> And with "native" KDevelop is simply
> unusable.

What exactly do you mean?  It seems to work great for me.


> As "opengl" only works well with accelerated graphics, "raster" is
> the only good choice. And as I said so far all of us using that engine have
> no problems with Qt4.5.2 and later, so this is a new bug you should report
> to the Qt developers.

Will do.


>> With all things considered, I don't think KDevelop should use raster on
>> it's own; IMHO that's a choice the user should make; apps should follow
>> the default unless the user says otherwise.
>
> Except if the default makes the app in question unusable. We want to
> provide a nice experience from the start, without the User having to dig up
> some obscure cmdline option.

This way we end up with each app circumventing defaults.  Imagine if 
each app would do that.  Users would have to configure each and every 
one separately and we're back to the 1980's.  Surely I'm not the only 
one who sees something wrong about this approach?  On most systems, Qt 
is not configured with raster as default, and there's a reason for that.

In any event, I don't feel too strongly about it, since now I know how 
to fix it.  Just mentioning that this might bite lots of people and it 
might be a good idea to make this configurable in KDevelop and using 
Qt's default by default.