DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2506
Version: 1.3-current
Fix Version: 1.3-current
Your patch seems to work fine too, see screen shot
Since my group name appears to be Domain Users,
the space in
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
Textual data can enter FLTK widgets by three means:
1) as character strings expressed in the program code
(e.g. button labels);
2) from keyboard
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
Aside from the matter of plain ol' bugs, the text displayed in widgets
might come from external sources like databases, network communication or
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2506
Version: 1.3-current
Fix Version: 1.3-current
Greg, I saw that this demo uses _WIN32 instead of FLTK's define WIN32.
This should probably be corrected as well.
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
Do you mean than instead of having a byte stream containing a series
of valid UTF-8 sequences of header byte and correct number of trailing
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
To be honest, I haven't checked the [already existing] code that validates
the UTF-8 string. I just noticed it seems to do a good job at
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2507
Version: 1.3-current
File name encodings are a bit of a pain as there is no clear right way.
What other toolkits do is to assume the file names are encoded according
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current
I agree that this seems like a sensible move, i.e. putting the HAVE_CAIRO
macro inside a fltk namespace by changing its name to be fltk
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current
Yup, looks like I did miss a few USE_CAIRO cases:
./src/Fl.cxx
./src/Fl_cocoa.mm
./src/Fl_Double_Window.cxx
./src/Fl_mac.cxx
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
Attached file fltk-1_v2.3.x-xft-check.patch...
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-currentdiff -up ./src/fl_font_xft.cxx.xft
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
Updated patch that also handles text measurements properly. Rendering of
stuff like selections got a bit funky otherwise.
Link:
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current
Note that one of the STRs resolved recently involved the use of
USE_CAIRO/HAVE_CAIRO in the CMake configuration files, and these
are probably
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2500
Version: 1.3.0
Mike, what do we need to do here? I have not used this tool before.
Link: http://www.fltk.org/str.php?L2500
Version: 1.3.0
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2507
Version: 1.3-current
On OS X, this seems to work well already. Could a Unix user please verify
and apply this?
Link: http://www.fltk.org/str.php?L2507
Version:
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
I am impartial to this. On the one hand, we never check parameters for
validity to keep the library fast. OTOH, we *do* put quite an effort into
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current
The macros in CMake are identical to those used in configure.in etc.. It's
all the same for configuring the CMake build and fltk-config etc. as
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2506
Version: 1.3-current
Fix Version: 1.3-current
Hmm, I'm thinking example code probably shouldn't assume special
FLTK build flags are set, since the context of
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current
Cairo in FLTK 1.3 can be seen similar to OpenGL. It merely gives you a
drawing canvas. The problem though is, if you link it dynamically, all
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2508
Version: 1.3.0
Mike suggested that he may have the time to upgrade those libraries. I
think that would be great, but I am afraid that we will have to change
some
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2505
Version: 1.3-current
Yes, I think that's right. The OP wrote: ... by doing a UTF-8 to
UCS-2/UCS-4 conversion, which has the side effect of filtering the
string.
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2506
Version: 1.3-current
Fix Version: 1.3-current
Well, should it then use any defined at all? Should the examples be
compilable on any platform, or should they be
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2506
Version: 1.3-current
Fix Version: 1.3-current
I figure since these are example programs, it's probably best
to use OS system calls in this case, where we're
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2506
Version: 1.3-current
Fix Version: 1.3-current
..in this case, 'ping'..
Correction: in this case 'dir' vs 'ls'..
Link: http://www.fltk.org/str.php?L2506
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current
I vote for just changing the macro names (and all source files that use
them :-( ), and that's enough to close this STR.
Everything else must
24 matches
Mail list logo
