I was just playing around and made a "MY_APP_TIMER = 28", which I manually sent to my main
window handle() function whenever 25ms had elapsed, e.g. mainWindow->handle(MY_APP_TIMER).
I'm not using Fl::run(), I'm using a while(1) loop that calls Fl:wait() and also calls a couple of functions
in my app, so the above call to handle() can happen in this loop without causing a reentrant call.
I guess calling this an "event" is not correct, but it's a value that doesn't collide with real FLTK events
which handle() can process. Obviously it's best if handle() always returns 1 for custom "event" values
so FLTK never tries to deal with them.
Anyway, it would be nice to have the FL_LAST_EVENT_[NUM] symbol for weird experiments like this.