Re: [fltk.development] [RFE] STR #2076:Patchforfl_text_extentsmechanismin fltk-1.3.x

2009-02-11 Thread matthiasm
On 11.02.2009, at 09:39, MacArthur, Ian (SELEX GALILEO, UK) wrote: ..so that one can easily just run through all the tests quickly just by clicking the 'Next Test' button, and it just selects the next item in the browser. Or just clicking in the browser will run that

Re: [fltk.development] [RFE] STR#2076:Patchforfl_text_extentsmechanismin fltk-1.3.x

2009-02-11 Thread Greg Ercolano
matthiasm wrote: When I ported FLTK to the Mac, I started exactly that. The source code is still in test/unittest.cxx. The goal was to be able to verify rendering on every available platform. I wanted to render markers first and then overwrite them with whatever drawing function I was

Re: [fltk.development] [RFE]STR#2076:Patchforfl_text_extentsmechanismin fltk-1.3.x

2009-02-11 Thread Greg Ercolano
MacArthur, Ian (SELEX GALILEO, UK) wrote: I think the browser idea might be a bit clearer and easier to navigate, so that it's always clear what all the tests are by name, and both keyboard or mouse could navigate the tests consistently. (The browser would simply remain

Re: [fltk.development] [RFE] STR #2076: Patchforfl_text_extentsmechanismin fltk-1.3.x

2009-02-10 Thread Greg Ercolano
Albrecht Schlosser wrote: Indeed, the test program attached to the STR might even be added to the test folder, if we wanted to go that far? +1 from me for the program in the test folder. Probably such a program could test multiple fltk functions, so that we don't set a