On 20.10.2010, at 08:55, Duncan Gibson wrote: >> OTOH, if you call fl_draw() and didn't set a font before calling >> it, then we could probably set a default font ... > > I think the simplest would be to have an assert or other check that > a font has been set, so that the user isn't left scratching his/her > head wondering why there's a segmentation fault.
Yes, I think that we should do at least some fundamental checks to prevent a crash, but I'd prefer to set a default font, as it seems to be done for some platforms. But it's definitive dependent on the platform and configuration (e.g. XFT). We need to check all platforms. >> Duncan, on which platform (and if Linux: w/ or w/o XFT) did you >> run your program? > > I installed fltk-1.3.x-r7677 on my work box back in July, with XFT. > It's a 64-bit box, with CentOS 5.5 installed, but it's taken several > updates to get to this point. My home box is 32-bit, running Lunar > Linux which is a rolling distro but I haven't updated it since August, > and I just re-installed fltk-1.1.10 on it to develop the example. > Off the top of my head I don't know whether XFT is installed, but I > would imagine so. Note that it's not only the system configuration, but also FLTK's configuration that matters. FLTK 1.1's default is w/o XFT, whereas FLTK 1.3's default is with XFT (if available). Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
