If that's added and a few bugs are fixed I'd vote to have a major fltk2
release.
I argued in that direction many years ago, but that didn't seem so important
for some of us who decided to continue experimentation on fltk2 adding new
unstable features, thus adding again new bugs, in an endless
I'll throw in my $.02 here
Me too.
[..]
The vast majority of widget labels tooltips are compile time constants
Other than your own apps, do you have any evidence whatsoever
to support this statement?
anyways, why add the extra overhead that's not needed?
And it integrates wonderfully well
Brian wrote:
Also arguing that replacing char* by std::string and so on would make FLTK2
more bug free is a complete...
Using std::string *would* make fltk2 more bug free.
But it would be a mistake.
Maybe it could be a compile time option to enable std::string()
methods.
[EMAIL PROTECTED] wrote:
The vast majority of widget labels tooltips are compile time constants
Other than your own apps, do you have any evidence whatsoever
to support this statement?
I also disagree with saying that majority of labels are compile time
constant, because:
1) mostly:
