[QScintilla] Display issue on windows

[Phil Thompson]

On Thu, 7 Apr 2011 19:43:58 +0200, Detlev Offenbach
<detlev at die-offenbachs.de> wrote:
> On Donnerstag, 7. April 2011, christophe duvernois wrote:
>> This is working setting the font quality to
>> SC_EFF_QUALITY_NON_ANTIALIASED
>> ( = 1) instead of SC_EFF_QUALITY_DEFAULT (= 0 ) .
>> I have now the same render (on windows) as with 2.4.x !
>> 
>> Thanks!
>> 
>> Chris.
>> 
>> 2011/4/7 Phil Thompson <phil at riverbankcomputing.com>
>> 
>> > On Thu, 7 Apr 2011 00:29:35 +0200, christophe duvernois
>> > 
>> > <christophe.duvernois at gmail.com> wrote:
>> > > Hi
>> > > 
>> > > - The following code on windows with qscintilla 2.5 doesn't have
the
>> > 
>> > same
>> > 
>> > > render on screen as with 2.4.6
>> > > the "courier new" font was "clear" on 2.4.6 but on 2.5 the font
>> > > display
>> > 
>> > is
>> > 
>> > > kind of blurred.
>> > > Any ideas??
>> > > 
>> > > #include <QApplication>
>> > > #include <Qsci/qsciscintilla.h>
>> > > #include <Qsci/qscilexercpp.h>
>> > > 
>> > > int main(int argc, char* argv[])
>> > > {
>> > > 
>> > >     QApplication app(argc, argv);
>> > >     
>> > >     QsciScintilla *qscintilla = new QsciScintilla;
>> > >     qscintilla->setUtf8(true);
>> > >     
>> > >     QsciLexerCPP *lexer = new QsciLexerCPP;
>> > >     lexer->setDefaultFont(QFont("Courier New",10));
>> > >     
>> > >     qscintilla->setLexer(lexer);
>> > >     
>> > >     qscintilla->show();
>> > >     return app.exec();
>> > > 
>> > > }
>> > > 
>> > > - Although, is there a way to get or check out somewhere the old
>> > 
>> > released
>> > 
>> > > version of qscintilla?
>> > > 
>> > > Regards.
>> > > Chris.
>> > 
>> > You could try experimenting with SCI_SETFONTQUALITY. I'm happy to
>> > change
>> > the default if it is shown to be incorrect.
>> > 
>> > Phil
> 
> Should this be part of the API so users can configure it for their
system?
> If 
> it is just give me a hint because I didn't spot it in the docu.

I'm happy to add something to the high-level API, but more importantly the
default needs to be correct.

I've made a change in tonight's snapshot which should restore the previous
default behaviour. If people can confirm it works then I'll make a new
release.

Phil