> > ALSO: perhaps it's no longer needed, but I thought FLTK apps > that used the FLTK image library had to call: > > fl_register_images(); > > ..at the top of main() to ensure the lib properly initialized. > So you should try adding that as the first thing in your main().
Actually, I do think this is maybe key after all... I've been staring at the OP's code, and his comments describe the failure mode, it *really* sounds like it has that sort of Heisenbug character that you get from unallocated buffers, so I now thinks that the behaviour is caused by him not registering the image functions. Windows has (in my unfortunate experience) been tolerant of bad buffer handling, inevitably leading to hard-to-trace bugs. (I remember that a while ago I had a big app that had always "worked" fine while I developed it (on a WinXP box) that died horribly when I moved it to OSX. There was a *really heinous* buffer overflow in the code that had never shown up, but the OSX memory manager spotted it straight away....) So, anyway, I think the register_images thing is the key difference between my tests and the OP's code, and will help here! _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
