|
From: <tim...@en...> - 2006-09-10 17:11:22
|
Richard Henwood wrote:
> Timoth=C3=A9e Lecomte wrote:
>
> =20
>> Richard Henwood wrote:
>> =20
>>> Timoth=C3=A9e Lecomte wrote:
>>>
>>> <snip previous conversation>
>>> =20
>> <snip again>
>>
>> Richard, can you also try without oversampling ? ("Rendering method =3D
>> antialiasing" or "no antialiasing")
>>
>> =20
>
> After switching to "without oversampling on both 'antialiasing' or 'no
> antialiasing'" the fonts look fine. However I need to close wxt term an=
d
> reopen in order to get this working predictably.
> =20
Typically you change the rendering method, click 'Ok' or 'Apply', and=20
type 'replot' in the command line. Closing the terminal should not be=20
needed (all the more since it only hides the window but does not do=20
anything else actually), exiting gnuplot should not be needed too.
So, the bug only appears when the rendering method is set to=20
'Antialiasing and oversampling', right ?
Can you tell me if a font of size 200 with 'Antialiasing and=20
oversampling' looks exactly the same as a size of 10 without=20
'oversampling' ?
(the oversampling precisely involves a scaling of 20)
> If I make the changes to the rendering method and then resize, without
> closing/reopening the result is unpredictable, including: huge fonts, o=
nly
> some text displayed, graphics become pixelated, even a lockup.
> =20
Indeed. For this to work as expected, I would have not to change the=20
internal variables immediately, but schedule the change for the time of=20
the next plot. Maybe I should do that before the release...
> HTH
> r,
> =20
Best regards,
TImoth=C3=A9e
|