I'm playing around with allowing dialogs generated by dialog plugin to be unicode.
Q1: could be done either with one more parameter stuck on the end of define service (12th or 15th, depending on whether separate X Y W H args used)). or be done by define_unicode, same args as define If the former, could add a config ini key to determine the default creation mode for dialogs (unicode/ANSI) Q2: should there be a similar parameter for controls (otherwise all ANSI dialogs would have ANSI controls, and unicode dialogs unicode controls). There are special cases: activex (AtlAxWin class) seems to be neither one nor other (as no text involved) richedit 5.0 (MSFTEDIT_CLASS class) (if I implelent it) seems to be unicode-only Note all this is separate issue from being able to get/send unicode strings in messages to out-of-process contrlls
