MacArthur, Ian (SELEX GALILEO, UK) wrote:
> This is fltk-2 you are using?
> I don't use fltk-2 that much myself, but it should work entirely in
> UTF-8 internally.
> Indeed, it may even have the support you need to "just work" in win98m
> but I don't know for sure, maybe some of the fltk-2 team can chip in
> here?
After looking at the sources, FLTK (2) seems to be very well thought in this
respect - it detects lack of unicode at runtime, and then uses -A versions
of WinAPI functions, and seems to do all conversions unicode<->A(encoded).
>> Also, how to detect if Im on win98?
> Oh, now you're asking... It's been a while...
About unicode, the function is: int has_unicode()
> I think you call GetVersionEx(..) and decode the returned structure,
> looking at the platformID to discriminate between win9x and winNT series
> variants. Googling for GetVersionEx ought to turn something up.
Yes, it is indeed used here :)
// src/win32/run.cxx
int has_unicode()
{
static int has_unicode = -1;
if (has_unicode == -1) {
OSVERSIONINFOA os;
os.dwOSVersionInfoSize = sizeof(OSVERSIONINFOA);
GetVersionExA(&os);
has_unicode = (os.dwPlatformId==VER_PLATFORM_WIN32_NT);
}
return has_unicode;
}
> Do you have to support a lot of win98 users? That could get to be a real
> problem...
Yes, I have to. But so far, it looks optimistic.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
