--- In [email protected], "Sheri" <sheri...@...> wrote:
>
> --- In [email protected], "entropyreduction"
> <alancampbelllists+yahoo@> wrote:
> >
> > --- In [email protected], "Sheri" <sherip99@> wrote:
> ...unless the target provided to choose_font doesn't support getting
> its font, then the service gives an error (wrong number of arguments).
Does this still happen with dialogplugin1.19_081219.zip?
> If the target provided to choose_font is the handle to a whole bar,
> font dialog opens with Microsoft Sans Serif and an absurdly large font
> size of 721788. Properties for the tested bar actually had:
> TempBar.NewProperties(?"fontname = Arial\nfontinfo = Bold Size: 10")
Does this still happen with dialogplugin1.19_081219.zip?
> Using get_value to get the font, the following crashes PowerPro:
> local TestBarhandle=cl.getbarhandle("TestBar")
> win.debug(dialog.get_value(TestBarHandle, "font"))
Does this still happen with dialogplugin1.19_081219.zip?
> It also crashes PowerPro if you use get_value to try to get the font
> for a window with class PowerProChildToolbar.
Does this still happen with dialogplugin1.19_081219.zip?
> If an individual *control item has its own font (via cl.setfont),
> dialog.get_value(controlhandle, "font") gets its fontspec accurately
> without crashing. Ditto for choose_font.
Does this still happen with dialogplugin1.19_081219.zip?
