1. startup fonts in win32lib
...since I read D. Parnell's complaints about small fonts at SourceForge,
here's another similar ( and old ! ) suggestion:
----------------------------------------------
atom transColor -- ** ( around line 6223 in current Win32Libex )
-- NEW! 0.45r system font ANSI_VAR_FONT instead of SYSTEM_FONT
-- NEW! 0.45l added NullBrushID
atom DefaultFontID -- ** new ( instead of constant )
global procedure setStartupFont(integer font) ----** new procedure
DefaultFontID = c_func( xGetStockObject, { font } )
end procedure
setStartupFont(ANSI_VAR_FONT) --** sets usual 'tiny' default font
-- NEW! 0.45r system font ANSI_VAR_FONT instead of SYSTEM_FONT
-- NEW! 0.45l added NullBrushID
constant
-- null brush
NullBrushID = c_func( xGetStockObject, { NULL_BRUSH } ),
-- default font
-- ** DefaultFontID = c_func( xGetStockObject, { ANSI_VAR_FONT } ),
------------------------------------------------
This allows you to change the default font for your whole program using any
of:
OEM_FIXED_FONT, ANSI_FIXED_FONT ,
ANSI_VAR_FONT, SYSTEM_FONT, or SYSTEM_FIXED_FONT
...just by doing something like:
include win32lib.ew
setStartupFont(SYSTEM_FONT)
Wolf
2. Re: startup fonts in win32lib
Ummmm, actually I didn't complain. I just responded to Dan's observation. I
like your approach to the problem as it is similar to other changes I've
been including. I'll insert your code into the current WIP code, unless you
tell me otherwise.
---
cheers,
Derek
----- Original Message -----
From: "wolfgang fritz" <wolfritz at king.igs.net>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Friday, August 18, 2000 6:15 AM
Subject: startup fonts in win32lib
> ...since I read D. Parnell's complaints about small fonts at SourceForge,
> here's another similar ( and old ! ) suggestion:
>
> ----------------------------------------------
> atom transColor -- ** ( around line 6223 in current Win32Libex )
>
> -- NEW! 0.45r system font ANSI_VAR_FONT instead of SYSTEM_FONT
> -- NEW! 0.45l added NullBrushID
>
> atom DefaultFontID -- ** new ( instead of constant )
>
> global procedure setStartupFont(integer font) ----** new procedure
> DefaultFontID = c_func( xGetStockObject, { font } )
> end procedure
> setStartupFont(ANSI_VAR_FONT) --** sets usual 'tiny' default font
>
> -- NEW! 0.45r system font ANSI_VAR_FONT instead of SYSTEM_FONT
> -- NEW! 0.45l added NullBrushID
> constant
> -- null brush
> NullBrushID = c_func( xGetStockObject, { NULL_BRUSH } ),
>
> -- default font
> -- ** DefaultFontID = c_func( xGetStockObject, { ANSI_VAR_FONT } ),
>
> ------------------------------------------------
>
> This allows you to change the default font for your whole program using
any
> of:
> OEM_FIXED_FONT, ANSI_FIXED_FONT ,
> ANSI_VAR_FONT, SYSTEM_FONT, or SYSTEM_FIXED_FONT
>
> ...just by doing something like:
> include win32lib.ew
> setStartupFont(SYSTEM_FONT)
>
> Wolf
3. Re: startup fonts in win32lib
I like Wolf's simpler variation, as it gives more options than the one I
submitted.
I'm wondering if you are continuing to use David's internal
"self-documenting" feature (with "makedoc"), which creates html
documentation directly from special comments inside Win32Lib, & if you have
things like that explained somewhere on SourceForge?
And where's the *real* programming traffic for the project; there must be
more going on than my few comments in its forum?
Dan
----- Original Message -----
From: "Derek Parnell" <dparnell at BIGPOND.NET.AU>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Thursday, August 17, 2000 1:46 PM
Subject: Re: startup fonts in win32lib
> Ummmm, actually I didn't complain. I just responded to Dan's observation.
I
> like your approach to the problem as it is similar to other changes I've
> been including. I'll insert your code into the current WIP code, unless
you
> tell me otherwise.
>
> ---
> cheers,
> Derek
>
> ----- Original Message -----
> From: "wolfgang fritz" <wolfritz at king.igs.net>
> To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
> Sent: Friday, August 18, 2000 6:15 AM
> Subject: startup fonts in win32lib
>
>
> > ...since I read D. Parnell's complaints about small fonts at
SourceForge,
> > here's another similar ( and old ! ) suggestion:
> >
> > ----------------------------------------------
> > atom transColor -- ** ( around line 6223 in current Win32Libex )
> >
> > -- NEW! 0.45r system font ANSI_VAR_FONT instead of SYSTEM_FONT
> > -- NEW! 0.45l added NullBrushID
> >
> > atom DefaultFontID -- ** new ( instead of constant )
> >
> > global procedure setStartupFont(integer font) ----** new procedure
> > DefaultFontID = c_func( xGetStockObject, { font } )
> > end procedure
> > setStartupFont(ANSI_VAR_FONT) --** sets usual 'tiny' default font
> >
> > -- NEW! 0.45r system font ANSI_VAR_FONT instead of SYSTEM_FONT
> > -- NEW! 0.45l added NullBrushID
> > constant
> > -- null brush
> > NullBrushID = c_func( xGetStockObject, { NULL_BRUSH } ),
> >
> > -- default font
> > -- ** DefaultFontID = c_func( xGetStockObject,
{ ANSI_VAR_FONT } ),
> >
> > ------------------------------------------------
> >
> > This allows you to change the default font for your whole program using
> any
> > of:
> > OEM_FIXED_FONT, ANSI_FIXED_FONT ,
> > ANSI_VAR_FONT, SYSTEM_FONT, or SYSTEM_FIXED_FONT
> >
> > ...just by doing something like:
> > include win32lib.ew
> > setStartupFont(SYSTEM_FONT)
> >
> > Wolf
4. Re: startup fonts in win32lib
Dan Moyer wrote:
>
> I'm wondering if you are continuing to use David's internal
> "self-documenting" feature (with "makedoc"), which creates html
> documentation directly from special comments inside Win32Lib,
> & if you have
> things like that explained somewhere on SourceForge?
>
> And where's the *real* programming traffic for the project;
> there must be
> more going on than my few comments in its forum?
>
Sorry, I've been sporadically taking a look at sourceforge, but I haven't
really had time to contribute there. The method for posting code is a bit
complicated, and I think I'll just send my stuff to Derek to put up--for
now, at least. :)
Right now I'm working on the documentation, in the same format as Dave used.
I should have that done within the next few days. I've also polished up
some of the code, moving some of the routines into existing routines (like
getLVItem -> getItem). As I mentioned a couple days ago, I've also made the
image lists a bit more versatile, allowing xpms and eu bitmaps to be added.
I've received some requests (which I agree with--it's time to get my act
fully together :) to put out an official version. Of course, I can't do
this by myself. I figure the first step will be to put the code up on
sourceforge (it'll be on my site, too, of course), and then have it added
to, modified, and blessed by the powers that be.
I've put up what I've got so far at
Matt
Matt
