Alvin wrote:
> I wonder though, when dealing with URLs as the payload, would it be
> appropriate for the FLTK DND system to massage the URL into some standard
> FLTK form. For example, fl_dnd_x.cxx::Fl::dnd() does some checking to see
> if the URI is a "common URI scheme".
One thing to keep in mind is FLTK apps can communicate to each other
with free form text strings through DND which are not URIs. So
wouldn't want that as "default" behavior.
Could maybe be a separate fl_uri_convert_dnd() or some such that
could post process the DND string, as long as it doesn't bring in
a dependency on external libs (like iconv(3)).
Sometimes FLTK allows external dependencies as compile-time options..
but it gets tough for support. Sometimes it's best to let the app folks
figure out how to deal with such things, or with external packages.
When external package starts looking stable, and like it should really
be brought into FLTK, the core dev folks will consider it.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk