DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2766
Version: 1.3-feature


I think this would be good for those starting to use fltk or those who
don't use 3rd party fltk libraries.  For those just starting, they can use
the macros easily and those wanting to covert can do so easily as well. 
For example things that used to be "some text @-> more txt" can be
converted by "some text " FL_SYMBOL_CHAR "-> more text" (easy) where as
you couldn't do "some text " Fl::symbol_str("->") " more text" (gonna be
work).  Also, the macros could always be converted to fit any future
solution that could work out how to return symbol strings in static
buffers (or whatever other solution that could be used).  I'd hate to see
it not used and 1, 2 or more years from now there was no solution added. 
For those creating 3rd party libraries where they only want to provide one
version, a single variable could be setup to contain the symbol char that
they could use to build up their custom strings internally.  While I agree
keeping it all in variables and assignable would be great (which was my
fist thought as well and what I've done for all the other optional items),
there may be too many issues for it to be practical.  However, I do think a
variable should be added for those 3rd party library providers.


Link: http://www.fltk.org/str.php?L2766
Version: 1.3-feature

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

Reply via email to