> Another useful test would be to add
>
> fl_alert("after Fl::run()";
>
> at the end of the program (as it says, after the Fl::run()
> statement) to see if Fl::run() is terminated and the program
> hangs somewhere in the destructors or other Windows runtime
> code.
>
> This code at the end of test/device.cxx works as expected
> here on Windows 7:
>
> --- end of test/device.cxx ---
>
> Fl::run();
> fl_alert("after Fl::run()");
> return 0;
> };
> Albrecht
Excellent suggestion. Let's see what Domingo finds.
On a different argument: I'm confused about image printing on the
Win platform: I see images printed well on my mac with the
VirtualBox XP virtualizer, but when I transfer the .exe's on a
real XP box, images (transparent or not) don't print at all!
I'm lost! What do you see on real MSWindows computers regarding
printing of Fl_RGB_Images ?
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
