It still seems to work ok when the target is provided and no color variable requested (e.g. CA).
I tested the new format using values retrieved from non-control bar items. Existing cl commands let us set, but not get, most font information. For getting, we have only cl.getFontName. Choose_font does currently work ok for initializing if given a fontface only when the size and other attributes are omitted, and the provided fontface has no spaces in it. If the retrieved fontname has any space in it, it doesn't work with name only. I constructed what I think should be a complete valid font spec by surrounding the fontname with double quotes and tacking three spaces and 10.0 on the end. But that doesn't work either. The form I was using was: dialog.choose_font(<font_spec>, <var_for_colour>) Question on dialog font service vs. *controls in bars. dialog can get and set fonts as well as background color for *controls on bars control that supports such things. Not sure what's up with foreground color. I know that at least with fonts there are resource implications, that a font is created that needs to be destroyed. What if anything does the dialog plugin do to ensure that the created font is destroyed when no longer needed? Can I repeated use dialog's font services on a given control without worrying about it? Regards, Sheri
