michael sephton wrote:
> Thanks for the speedy helpful reply. I realise now if i had re-read the
> documentation on Fl::copy, http://www.fltk.org/doc-1.1/Fl.html#Fl.copy, i
> could have guessed the cause of my problem. Perhaps it could be added to
> those docs that using the wrong clipboard for the wrong type of copy
> operation results in the dreaded segfault, to make the rule easier to
> remember...
>
> Thanks for cleaning up that demonstration program as well, i hope it is
> useful for someone. By the way, what is the preferred procedure for adding
> tests, or improving the docs? Is it simply to make the suggestion on this
> message board, after which the lead developers can choose how to use it when
> they are updating the docs/distribution?
Actually, making an STR is the way to request changes to the docs, make bug
reports,
and post requests for enhancements (RFE's):
http://fltk.org/str.php
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
