DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2672
Version: 1.3-feature
Here there is the modified version of fl_gleam. I think it looks better
with the gradients on the top and the bottom, so the the middle area of
Here there is the modified version of fl_gleam. I think it
looks better
with the gradients on the top and the bottom, so the the
middle area of
the widgets it is no strongly affected. Here an screen shot:
https://sites.google.com/site/eetorres/fl_gleam
The new gleam can be found
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2672
Version: 1.3-feature
A few minor comments:
- It looks to me as if the patch changes the behaviour of
Fl_get_system_colors for all schemes, not just for the gleam
Just refreshed my fltk3 snapshot - fails with the following errors.
(NOTE: I don't think I've ever seen one of those errors before, now we
have several!)
Compiling Fl_File_Chooser2.cxx...
Fl_File_Chooser2.cxx: In member function `void
fltk3::FileChooser::fileNameCB()':
Fl_File_Chooser2.cxx:870:
On 20.06.2011, at 11:39, MacArthur, Ian (SELEX GALILEO, UK) wrote:
Just refreshed my fltk3 snapshot - fails with the following errors.
(NOTE: I don't think I've ever seen one of those errors before, now we
have several!)
Compiling Fl_File_Chooser2.cxx...
Fl_File_Chooser2.cxx: In
What I'd suggest doing is simply explicitly casting the first
parameter
to a char*; this _should_ fix your issue (at least it doesn't
create any
on gcc under Ubuntu 10.10).
I suspect the only person who could confirm such a fix would be Ian,
though
Yes, that does work, e.g:
// fltk3::alert(%s,existing_file_label); // error
fltk3::alert((char*)%s,existing_file_label); // ok
Though I have concerns about casting a fixed string like
that just to
trick the compiler into doing the obvious conversion.
From what I understand of the mechanics
Yup - my worry is that if we use %s like that, the compiler will
create a const char array, we then cast away the const-ness, and
(conceivably) could then write to that string - segfault, bad.
So I'm not keen on casting away the inherent const-ness of the fixed
string...
Though in practice
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2641
Version: 1.4-feature
Attached patch fullscreen17.patch, update patch to better deal with the
Windows coordinate mess and to fix windows starting in fullscreen.
[..]
There are two, being:
A) FLTK3_EXPORT void alert(const char *,...) __fl_attr((__format__
(__printf__, 1, 2)));
B) FLTK3_EXPORT void alert(va_list, const char *);
const issues aside, (A) says there's an fl_alert() that
takes a char* argument and some other arguments,
while (B)
No need to fiddle something. The va_list version is only there to support the
sealers and would be rarely used by an app developer. Somewhat like fprint vs
vfprint. All we need to do is rename the second fltk3::alert to fltk3::va_alert
and the ambiguity is gone. It's interesting that va_list
No need to fiddle something. The va_list version is only
there to support the sealers and would be rarely used by an
app developer. Somewhat like fprint vs vfprint. All we need
to do is rename the second fltk3::alert to fltk3::va_alert
and the ambiguity is gone. It's interesting that
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2672
Version: 1.3-feature
For a strict adherence to the CMP, all features need to be pushed to 1.4 or
later.
Link: http://www.fltk.org/str.php?L2672
Version:
On Jun 20, 2011, at 5:24 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I just noticed I mis-spelled the lib name in the title; fltk or flth
anyone?
The first option that the compiler offers is the one expanding
alert(va_list, const char *); where the va_list is
expanded here as a
char*,
Ahrgh. Go into the fltk directory and run make depend. I keep forgetting to
do that before I run svn commit and after make clean.
On 20.06.2011, at 16:30, MacArthur, Ian (SELEX GALILEO, UK) wrote:
No need to fiddle something. The va_list version is only
there to support the sealers and
On 20.06.2011, at 16:43, Michael Sweet wrote:
On Jun 20, 2011, at 5:24 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I just noticed I mis-spelled the lib name in the title; fltk or flth
anyone?
The first option that the compiler offers is the one expanding
alert(va_list, const char *);
Ahrgh. Go into the fltk directory and run make depend. I
keep forgetting to do that before I run svn commit and
after make clean.
The makedepend file appears to be configured - so I just hand edited it
to fix the one typo and commited that, it then seems to work just fine
right up until
On 20.06.2011, at 16:41, fltk-dev@easysw.com wrote:
Author: ianmacarthur
Date: 2011-06-20 07:41:23 -0700 (Mon, 20 Jun 2011)
New Revision: 8835
Log:
Trivial mod to makedepend to get test1 folder to build on Msys/mingw.
Now builds as far as colbrowser...
Yes, colbrowser is where it's
On 20.06.2011 17:42, MacArthur, Ian (SELEX GALILEO, UK) wrote:
Ahrgh. Go into the fltk directory and run make depend. I
keep forgetting to do that before I run svn commit and
after make clean.
The makedepend file appears to be configured - so I just hand edited it
to fix the one typo and
On 20.06.2011, at 18:11, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I'm frequently updating the makedepend files in the fltk 1.3 branch,
but yes, they should be updated and committed in fltk 3 branch as
well. I do suspect, however, that running make depend after make
clean wouldn't work,
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2672
Version: 1.3-feature
Attached file gleam-fltk-1.3.x-rev8836.patch...
Link: http://www.fltk.org/str.php?L2672
Version: 1.3-featureIndex: src/fl_gleam.cxx
21 matches
Mail list logo
