Albrecht Schlosser schrieb:
>> I know this working (using another approach, see my template example)
>> and it's fine - when there is a high resolution monitor, you just need
>> to resize the window, save size and the whole software is adjusted to
>> the current resolution.
>
> Probably only if al
> There's no way to change this with a configure option or an environment
> variable, but I modified the check to look for "/usr " (note the
> trailing space) in the first place, so that I could simplify the check.
> I hope this works for your and doesn't break other MinGW installs.
Tried out your
On 04/16/12 11:14, Edzard Egberts wrote:
> > Since FLTK is targeted at platforms which often lack complete ISO C++
> > support or have limited memory, all C++ code in FLTK must use a
> > subset of ISO C++.
>
> What's about today, are these restrictions state of the art?
>
> Exceptions
>
+1 to modernize C++ usage of FLTK, as mentioned before using char* to
represent strings is a bit low level compared with the facilities that c++
offer. Also reinventing Arrays here and there.
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.c
Greg Ercolano schrieb:
> On 04/16/12 11:14, Edzard Egberts wrote:
>> I'm in doubt of Exceptions, but I love using STL and I don't like char*.
>> To me it's not C++ without STL, at the very most a C+.
> However, FLTK 3.x might be an opportunity to draw the line
> between 'ancient' compil
I'd like to get FLTK into Continuous Integration in an attempt to make it
compile and link on all platforms at all times.
http://www.martinfowler.com/articles/continuousIntegration.html
I have set up a few old AMD 64 bit machines that were still laying dormant
around the house, and I now want
6 matches
Mail list logo
