matthiasm wrote: > > Fl_String: basically typedef'd to "char*" (UTF-8 encoded unicode), but > on WinCE, it would be WCHAR* > Fl_Char: a single Unicode character (32-bit), or WCHAR on CE > Fl_Shortcut: a Unicode character pls flags for modifier keys (alt, ctrl, > etc.) >
I do not like that too much. It would be better to use an internal utf-to-WCHAR translation functions on WinCE (or other platforms which do not have particular utf-8 api). What if a user wants to use some standard string functions with these beasts? They would probably work just fine with utf-8 strings but fail with WCHAR implementation. That would break a lot of code on such platforms. Also we should avoid introduction of various cryptic types. This has always been what I like about FLTK - the use of standard types at api level. It might be little bit pain to keep binary compatibility but it is very refreshing for a programmer to see "int" instead of "some_library_size_t_for_function_foo". I vote for old good "char *" as the name for our newborn son, fltk uft-8-capable string. In the end, that is what utf-8 is all about, isn't it? Roman _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
