1. Win32Lib v0.60
Derek,
I must say, I'm not a fan of the new default font scheme. It was a bit
of a surprise that the fonts in my Win32Lib apps were suddenly different.
Is there any way to turn this off unless asked for? I understand that
whatever the default is may not be pretty, but it's good to have a Eu
app look like other apps IMHO.
Also, the environment variable thingy doesn't seem to work. Using the
format specified in the Docs:
w32Defaults=Font:{Comic Sans MS,12,3}
doesn't work. Your parsing routines don't separate the arguments
correctly. If I remove the {} then it splits things, and recognizes
the face name, but not anything else.
The docs say that the Defaults system is an application specific way
to change things. I didn't see anything specific, other than to use
the OS SET command, which doesn't seem to work from within Eu. There
don't seem to be any demos using this feature. Could you please elaborate
on how this is supposed to work?
It seems that calling setDefaultFont() on a created window returns things
to normal, but this seems like an awful (and needless) workaround.
Matt Lewis
2. Re: Win32Lib v0.60
Matt Lewis wrote:
>
> Derek,
>
> I must say, I'm not a fan of the new default font scheme. It was a bit
> of a surprise that the fonts in my Win32Lib apps were suddenly different.
> Is there any way to turn this off unless asked for? I understand that
> whatever the default is may not be pretty, but it's good to have a Eu
> app look like other apps IMHO.
>
> Also, the environment variable thingy doesn't seem to work. Using the
> format specified in the Docs:
>
> w32Defaults=Font:{Comic Sans MS,12,3}
>
> doesn't work. Your parsing routines don't separate the arguments
> correctly. If I remove the {} then it splits things, and recognizes
> the face name, but not anything else.
>
> The docs say that the Defaults system is an application specific way
> to change things. I didn't see anything specific, other than to use
> the OS SET command, which doesn't seem to work from within Eu. There
> don't seem to be any demos using this feature. Could you please elaborate
> on how this is supposed to work?
>
> It seems that calling setDefaultFont() on a created window returns things
> to normal, but this seems like an awful (and needless) workaround.
There are two mistakes I made here. The first is that the documentation
is wrong about the w32Defaults setting. Instead of '{}' braces it should
have '()' parenthesis. The second is that I left my 'test' font hardcoded
as the default font. Find the line ...
FontDefaults = { "verdana", 8, 0, Black }
and change it to ...
FontDefaults = { "ms sans serif", 8, 0, Black }
This should restore its behaviour to pre v0.60.
Sorry about the stuff up.
--
Derek Parnell
Melbourne, Australia
3. Re: Win32Lib v0.60
I am actually very happy with the new Win32lib. It seems to be running
alot faster for drawing routines, which is a major plus for me. And the
new functions are very well done as far as I can tell. I am quite
pleased with this.
Thanks for all your hard work,
Mario
