Re: tiny fonts with wxt term

[<tim...@en...>]

Timoth=C3=A9e Lecomte wrote:
> Richard Henwood a =C3=A9crit :
>  =20
>> Timoth=C3=A9e Lecomte wrote:
>>  =20
>>    =20
>>> So, the bug only appears when the rendering method is set to
>>> 'Antialiasing and oversampling', right ?
>>>    =20
>>>      =20
>> correct.
>>
>>  =20
>>    =20
>>> Can you tell me if a font of size 200 with 'Antialiasing and
>>> oversampling' looks exactly the same as a size of 10 without
>>> 'oversampling' ?
>>>    =20
>>>      =20
>> It does not look _exactly_ the same. The font appears to be the same s=
ize
>> but on switching there is some slight movement in exact positions of t=
ext.
>> It is very slight an I can only notice it because I watch it switch.
>>  =20
>>    =20
> Ok, I was interested in the size in particular. So it seems the=20
> oversampling scale is somehow not applied to the text on your setup.=20
> That's strange...
> Could you please try the demo 'enhancedtext.dem' and tell me if it show=
s=20
> the same issue ? (the text goes through a slightly different code path=20
> for the enhanced text mode).
>
> Another question, most likely unrelated : what's your screen dpi ?=20
> (dots-per-inch, this info is given by 'xdpyinfo' for example)
I hope I am not asking too much... Richard, could you please apply the=20
attached patch to your gnuplot checkout ? It will add a couple of=20
debugging messages that would help me greatly.

To apply the patch, go to the cvs checkout directory, and then:

cd src/wxterminal
patch -p1 < debug_richard.diff
cd ../..

Finally recompile with make; make install

Once you've done that, try with your favorite plot command ('test' is=20
fine) and please send me the output messages you obtain with and without=20
oversampling.

(we could also meet on irc, #gnuplot on freenode)

Thank you very much.

Best regards,

Timoth=C3=A9e