:WINDOWS-STATUS-FONT etc.

Hi!

This is mostly a question directed at the LispWorks team.  By playing
around I found out that on Windows one can successfully use
undocumented calls like this one

  (gp:make-font-description :stock :windows-status-font)

or replace :WINDOWS-STATUS-FONT with :WINDOWS-MESSAGE-FONT,
:WINDOWS-MENU-FONT, :WINDOWS-CAPTION-FONT, etc.

It seems like this is an easy way to access information that's
otherwise only available through ugly FLI calls to the likes of
SystemParametersInfo with a SPI_GETNONCLIENTMETRICS argument.

Is that correct and is this something that will be available in future
releases as well?

Thanks,
Edi.

Re: :WINDOWS-STATUS-FONT etc.

Hello Edi,

| This is mostly a question directed at the LispWorks team.  By playing
| around I found out that on Windows one can successfully use
| undocumented calls like this one
|
|   (gp:make-font-description :stock :windows-status-font)
|
| or replace :WINDOWS-STATUS-FONT with :WINDOWS-MESSAGE-FONT,
| :WINDOWS-MENU-FONT, :WINDOWS-CAPTION-FONT, etc.
|
| It seems like this is an easy way to access information that's
| otherwise only available through ugly FLI calls to the likes of
| SystemParametersInfo with a SPI_GETNONCLIENTMETRICS argument.
|
| Is that correct and is this something that will be available in future
| releases as well?

On my LWW 4.4.6, these stock font names do not work and result in fonts that
do not match those specified in Windows Control Panel.
--
Sincerely,
Dmitriy Ivanov
lisp.ystok.ru

Re: :WINDOWS-STATUS-FONT etc.

I wrote:

| On my LWW 4.4.6, these stock font names do not work and result 
|  in fonts that do not match those specified in Windows Control Panel.

My apologies - it does work. I have tried:

  (gp:make-font-description :stock :windows-caption-font :underline t)

which is obviously not in stock. Sorry for the noise.
--
Sincerely,
Dmitriy Ivanov
lisp.ystok.ru

Re: :WINDOWS-STATUS-FONT etc.

Unable to parse email body. Email id is 5273