I just noticed a few things on win32:
[1] If an app sets the window's xclass() *before* it sets the icon(),
the icon won't show up in the title bar.
[2] In the win32 osissues page, under "Setting the Icon of a Window"
there's a NOTE: that reads:
You must call Fl_Window::show(int argc, char** argv) for the
icon
to be used. The Fl_Window::show() method does not bind the icon
to the window.
This no longer seems to be true, at least empirically.
And I think Albrecht once commented he noticed this as well,
and wondered aloud if this comment was outdated, if ever true.
Is [1] known behavior that should be documented?
Is [2] really obsolete and should be removed, or are the empirical observations
simply undefined behavior?
Regarding [1], it was driving me nuts today, so if it really is order dependent,
we should document to prevent insanity.
In fact, I think when the following three calls are being used together,
they have to appear in this specific order or they won't work right..
at least on win32 anyway:
1) icon() -- if used with xclass(), this must be first
2) xclass() -- if used with icon(), this must come after icon()
3) show() -- if any of the above are used, this must come last
_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
