matthiasm wrote: > > On 29.03.2008, at 20:46, imm wrote: >>> >> Also, there's the WinCE port that Mikko_L posted back in June last >> year (was it that long ago?) - again, I haven't looked at it, but I >> think that "we" (in the wider sense, i.e. somebody, maybe even Mikko >> if he's around?) probably should look at it since it *must* have >> addressed wide-char issues to get it working at all on WinCE, and >> WinCE integration would be a Good Thing in the wider sense anyway. > > Yes. I suggest Fl types for strings and individual characters. Currently > I have: > > Fl_String: basically typedef'd to "char*" (UTF-8 encoded unicode), but > on WinCE, it would be WCHAR*
That's just a bad idea - you'd break source compatibility when compiling on WinCE. While we might have common UTF-8 conversion functions to go to UTF-16 at display-time, for example, we don't want to expose those implementation details to the application developer. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
