> --- In [email protected], "entropyreduction"
> <alancampbelllists+yahoo@> wrote:
>
> Just uploaded dialogplugin1.19_081224.zip
>
> To
>
>
http://tech.groups.yahoo.com/group/power-pro/files/0_TEMP_/AlansPluginProvisional/
>
> pdf, chm not up to date
>
>
> > > >
> > > > > If the target provided to choose_font is the handle to a whole
> > > > > bar, font dialog opens with Microsoft Sans Serif and an absurdly
> > > > > Properties for the tested bar actually
> > > > > had: TempBar.NewProperties(?"fontname = Arial\nfontinfo =
> > > > > Bold Size: 10")
Above was a typo, s/b
TempBar.NewProperties("fontname = Arial\nfontinfo = Bold Size: 10")
if the argument is literal, the \n needs evaluating.
> Fixed, I think.
Not clear if you were aiming to fix by actually retrieving the correct
values or just to default to System Bold 12 when the target is a whole
bar or its PowerProChildToolbar?
I created and showed TempBar. Used new dialog version to get_value,
"font" and choose_font on the resulting whole bar and child
PowerProChildToolbar.
New version still doesn't see the Arial, returns System
New version returns Bold
New version returns size 12 instead of size 10.
So new version is an improvement in that it doesn't crash or present
impossibly large size vaiues for whole bar or child toolbar handles,
but it doesn't retrieve the correct values. Perhaps document as a
limitation (unless there is a way to really fix it).
> Re destroying a font resource: suppose I provide
> a variant of dialog.clear e.g. dialog.clear(hwnd, "font")
> which will destroy the HFONT used by a window, and set it's
> font to the system font. To be used with care, only on
> powerpro-owned windows.
>
If asking, yes, I think that would be useful. Also possibly a
destroy_font service that would take an actual font handle (so dll
plugin wouldn't be needed in order to do it, e.g., if no window is
still using some known font handle that previously got created with
set_font).
Regards,
Sheri
