> I have both OSX and NT here.
Thanks !!! :)
> I take it for OSX you are just looking for a compile test which
> I can do easily enough.
Yes, just to check does it compiles fine without errors/warnings.
> Are there certain demos you want tested too?
One or two random chosen would be enough :)
> For windows, I have VS 6 on 2K and VS7 on XP, either of which
> I can use to compile (pick one ;) I can then run the demos on
> the NT box to check for runtime errors, assuming that's what you're
> looking for, or if you want me to exercise particular things I can
> do that if you can specify.
Yes, only for possible runtime errors, especially GetMonitorInfo in user32.dll.
AFAIK, GetMonitorInfoA is replaced with above more common, but we never
know what can pop up again :)
Bill recently updated VS7 files, which means they are pretty in sync with the
code.
> Anything in particular you want me to test?
> (STR#1635 didn't come with a test app, so not sure how to test for that)
Here is sample:
#include <fltk/Window.h>
#include <fltk/Widget.h>
#include <fltk/Cursor.h>
#include <fltk/run.h>
int main(int argc, char **argv) {
fltk::Window *window = new fltk::Window(300, 180);
window->begin();
fltk::Widget *b = new fltk::Widget(20, 40, 260, 100, "Cursor test");
b->box(fltk::UP_BOX);
window->end();
window->show(argc, argv);
window->cursor(fltk::cursor(fltk::CURSOR_DEFAULT));
return fltk::run();
}
Above sample will work on X11, but will probably crash on osx since
memcpy will get NULL parameter. At first I thought they added some protection
for
these cases, but it is oposite; maybe osx will slilently pass ?
--
Sanel
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
