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 up while one
cycles through the tests.)
[ Top-posting intentionally ]
After all the feedback we got, I summarize:
Fl_Smart_Pointer should not be used, because its name could be mistaken for
something that is different.
Fl_Widget_Guard should not be used either for similar reasons.
Our best bet would be Fl_Widget_Tracker, and this
matthiasm wrote:
No, you guys are correct.
Very nice, thank you!
Fixed; changed touched - overwritten.
Ian, also added a few more extents tests mainly out of curiosity..
I wanted to see what `, -, and _ looked like,
as well as some separate text with
