Hello,
Our team is developing a product that uses the toolkit intensively. At certain
point we will need UTF-8 support there. So, it's crucial for us to get an
estimate on when FLTK 1.3 is going to be released.
Would highly appreciate your answers.
Thanks.
_
> Our team is developing a product that uses the toolkit intensively.
> At certain point we will need UTF-8 support there. So, it's crucial
> for us to get an estimate on when FLTK 1.3 is going to be released.
Probably not until the 11 Open Feature Requests and 31 Open Bugs in
the development ver
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2351
Version: 2.0-feature
I should add that I fixed about a dozen of the test files but have still
not gotten the themes working because they are missing parts that can't
> Our team is developing a product that uses the toolkit
> intensively. At certain point we will need UTF-8 support
> there. So, it's crucial for us to get an estimate on when
> FLTK 1.3 is going to be released.
Hard to say - we are trying to clear the remaining STR's against it, but
resources
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2356
Version: 2.0-feature
This is a list of the twenty or so files that didn't compile at all
in the original version 2.x test directory and which were fixed and
modified
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2351
Version: 2.0-feature
Note that FLTK 2 was never released, it's a dev version that was far along,
but was still in dev when it went dormant. So expect to find things l
Hello!
Do you guys have some coding conventions for FLTK project?
I am looking at the code and it is all messed up. At least when editing in vim
indentation is bad, but of course that is not the biggest problem.
If there is, then every time somebody submits a new subversion it must be
checked (t
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2357
Version: 2.0-feature
Here's the preliminary (still testing) version of Fluid_Image.cxx that will
output the proper syntax for a SharedImage that's inlined.
That is
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2357
Version: 2.0-feature
Link: http://www.fltk.org/str.php?L2357
Version: 2.0-feature
Fluid_Image-syntax-fixup.tar.gz
Description: Binary data
On 29.04.2010, at 20:28, Emil Cataranciuc wrote:
> Do you guys have some coding conventions for FLTK project?
> I am looking at the code and it is all messed up. At least when editing in
> vim indentation is bad, but of course that is not the biggest problem.
The coding standards for 1.3 are he
Emil Cataranciuc wrote:
> Hello!
> Do you guys have some coding conventions for FLTK project?
> I am looking at the code and it is all messed up. At least when editing in
> vim indentation is bad, but of course that is not the biggest problem.
I'd suggest reporting indent issues with an S
11 matches
Mail list logo
