I sadly indeed believe that we should _completely_ drop NT4 otherwise we'll have lot of general questions and workarounds to deal with. One thing to also bear in mind, that relatively covers us is: the fltk 1.1.x (stable) version that we all use today will still be available to 9x/Mil./NT4 users ... So I think it's fair enough if you consider that we still deal with many different versions of the NT based kernel: Win2000,Xp,2003,Vista 32,Vista 64, etc ... IMHO, That already makes a lot for only one platform even if it's the most spread one. Fabien
> imacarthur wrote: > > > WinNT4 - it still mostly works (Albrecht said), but will probably get > > more broken as we add more UTF8 support and so forth... Can we *say* it > > is dropped, so that end-users are not too surprised, but not > > deliberately code to break it, at least in the short term? (I'm thinking > > of my fl_text_extents patch here; that outright broke WinNT4, but a > > little extra code to check for the missing methods allows it to run on > > NT and still do something reasonable there.) > > We could say that "Win9x/ME doesn't work" anymore (and maybe we should > check the version somewhere, before windows are opened, because I saw > that Win98 processes hung somewhere), and that "WinNT is not supported" > anymore, but _may_ work, if the user is lucky enough. Until another > addition really breaks it. > > OTOH, if we don't drop NT completely, there may be questions like "how > can I install a UTF-8-enabled font under WinNT ?" in the fltk news > groups, and I think that IME support is not available at all. > > Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
