Something seems to be screwed up.,.
Some of the tables now have a "100%" above the header.
For example on the startpage:
100% <--
Quickinfo
..
100% <---
Release Schedule
> On 02/22/12 10:14, Greg Ercolano wrote:
> > So I should be able to change soft
On 02/22/12 10:14, Greg Ercolano wrote:
> So I should be able to change software.php to do this:
> http://seriss.com/people/erco/fltk/tmp/fltk-downloads.png
>
> Basically adding an if() statement that checks to see if the version
> starts with "1." or not.
>
> Later, we can change that logic when
So I should be able to change software.php to do this:
http://seriss.com/people/erco/fltk/tmp/fltk-downloads.png
Basically adding an if() statement that checks to see if the version
starts with "1." or not.
Later, we can change that logic when one of the dev versions reaches
a release state.
On 02/22/12 09:13, Albrecht Schlosser wrote:
> I'd say its easier to do it locally once you've installed your own
> test environment.
Thanks for the advice.
Yes, got it all working in about 45 mins.
Just defaults for everything.
Installed LAMP and downloaded the
On 22.02.2012 17:14, Greg Ercolano wrote:
> On 02/22/12 03:20, Albrecht Schlosser wrote:
>> If you have a web server, mySQL and PHP on a Linux system, then
>> you can just download the whole FLTK env.
>
> Thanks, I might give that a try; the instructions on
> the 'website' downloads pag
On 02/22/12 03:20, Albrecht Schlosser wrote:
> If you have a web server, mySQL and PHP on a Linux system, then
> you can just download the whole FLTK env.
Thanks, I might give that a try; the instructions on
the 'website' downloads page seems to show how to
quickly setup my
On 21.02.2012 18:25, Greg Ercolano wrote:
> I think this could be solved by changing the php code
> in software.php to highlight the FLTK2 and FLTK3 releases
> *IN RED* with a header that says DEVELOPMENT USE ONLY,
> and perhaps even a click on the tar file would first pop
> > end to that this endless confusion with
> > users starting new development with FLTK 2 would have an end...
>
> I think this could be solved by changing the php code
> in software.php to highlight the FLTK2 and FLTK3 releases
> *IN RED* with a header that says DEVELOPMENT U
> On 19.02.2012 00:39, Bill Spitzak wrote:
>
> > I believe changing the scope of non-virtual methods is also ok. The
> > mangled name does not change.
>
> That's not true, according to the articles referenced below (see link).
> It seems to be true for gcc, however, but not for MSVC.
Actually,
