--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > Sorry, are next paras up to "==============" superceded > by > > > Seems to be working well now. If Bruce would add a few cl services > > ??
Well, it would be nice to have better error handling in the plugin even if Bruce adds those services. [snip] > Too fancy. > > And what happens if, in between, control's font is changed by > pproconf? Unlike if changed with dialog.set_font, the control must be reinitialized (get a new handle) before font changes to *control items via cl.setfont become visible. It is exactly the same with pproconf "Apply" and "OK". The bar gets a new handle and any child controls get new handles. So since the old one control ceased to exist, fancy event would destroy the old font. So to summarize the possibly too fancy suggestion, when using set_font on bar/non-native controls, dialog plugin would: 1. attempt to retrieve and destroy the old HFONT. If successful, also destroy any outstanding event polling for its destruction based on existence of the control handle. 2. make a new HFONT and select it into the requested control 3. make an event to periodically check for the existence of the control handle - if window doesn't exist, destroy the (new) HFONT. Means the bar got closed or refreshed or reconfigured through pproconf. Hopefully Bruce will comment. Regards, Sheri
