manolo gouy wrote:
> Albrecht:
> 
> - Many thanks for your explanations about the StretchDIBits bug;
> That'll help.

You're welcome. There is also one more problem I encountered because
I didn't know (and didn't find it in any general MS docs) that all
bitmaps must be aligned on 4 byte boundaries (per line), so that
you need fill bytes at the end of each pixel line (scan line). But
that's probably not the problem here.

> - Don't you believe we should remove the "Print front window"
> window of MSWin + X11 platforms before next friday's snapshot ?

Yes, I thought so, too.  We should put them inside
   #ifdef PRINT_FRONT_WINDOW
or similar to keep them for local testing, it someone wants to
have it again. Would you like to do it?

> - I would suggest to keep the corresponding Mac application menu
> item because it is probably useful and does no harm (I've removed
> its shortcut, so no interference with application programs).

Okay.

> - I've prepared for Fl_Sys_Menu_Bar class and fl_mac_set_about
> function to be seen by Doxygen. Could you, please, update again
> the site HTML documentation section ? The new Fl_printer
> and Fl_Device classes would then appear.

I've planned to do it at the weekend, after the appearance of the
next snapshot (and when I have more time). Thus we have still some
time to improve if it if needed.

> - I've declared a new "Module" called "Mac OS X-specific functions"
> to hold fl_mac_set_about, because my understanding is that functions
> must be in some module to be seen by Doxygen (Is that wrong?).

I'm not at all sure about that. For normal classes it works w/o modules,
but for functions w/o a class we will probably need a group/module.
I never bothered learning more about it, since Fabien did all this
grouping when we started doxygenation (maybe helped by Duncan).

> Is this module creation adequate ?

Yes, I think so.  Either one for each platform, or perhaps one for
"platform specific functions" for all platforms together.

Did you also see the lots of warnings when creating the docs?
Before the Fl_Printer addition we had only one or two warnings.
Do you have any plans or ideas how to reduce the warnings again?
Some look trivial, but others may be difficult to "repair".

Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to