gnuplot-bugs

Re: [Gnuplot-bugs] 1510055 win: font problem in enhanced text mode

[Bastian M. <bma...@we...>]

Ethan Merritt wrote:
> Did you have a chance to check if the suggested fix
> for this bug was correct?
>=20
> 	Ethan
>=20
I am sorry, but I didn't manage up till now. I am _very_ busy at
the moment ...

The order of the commands in WIN_font doesn't matter really.
GraphOp esentially builds a list of commands that the
windows terminal then uses to create the output at a later
point in time. WIN_font and WIN_fontsize are only needed
to track the font while processing enhanced text.

I think I found the bug, though: In WIN_enhanced_open() the
font was reset to the current font (WIN_font) instead of
the default font (see attachment). Stupid me.

Could someone else please test? I am posting this on the list
since SF is  not functional right now.

Bastian

--=20
Bastian M=E4rkisch
Physikalisches Institut, Universit=E4t Heidelberg

Re: [Gnuplot-bugs] 1510055 win: font problem in enhanced text mode

[Bastian M. <bma...@we...>]

Forgot attachment...

Bastian

Bastian Maerkisch wrote:
> Ethan Merritt wrote:
>> Did you have a chance to check if the suggested fix
>> for this bug was correct?
>>
>> 	Ethan
>>
> I am sorry, but I didn't manage up till now. I am _very_ busy at
> the moment ...
> 
> The order of the commands in WIN_font doesn't matter really.
> GraphOp esentially builds a list of commands that the
> windows terminal then uses to create the output at a later
> point in time. WIN_font and WIN_fontsize are only needed
> to track the font while processing enhanced text.
> 
> I think I found the bug, though: In WIN_enhanced_open() the
> font was reset to the current font (WIN_font) instead of
> the default font (see attachment). Stupid me.
> 
> Could someone else please test? I am posting this on the list
> since SF is  not functional right now.
> 
> Bastian
> 

Re: [Gnuplot-bugs] 1510055 win: font problem in enhanced text mode

[Ethan M. <merritt@u.washington.edu>]

On Thursday 29 June 2006 01:44 am, Bastian Maerkisch wrote:
>
> I am sorry, but I didn't manage up till now. I am _very_ busy at
> the moment ...

Understood.
I'm about to leave town myself, and won't be available
again until some time next week. 

> I think I found the bug, though: In WIN_enhanced_open() the
> font was reset to the current font (WIN_font) instead of
> the default font (see attachment). Stupid me.

There was no attachment, but I think I've understood you and
made the change.  Somebody please confirm whether or not that
was indeed the correct fix, so we can close the bug report.

-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle WA