DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2519
Version: 1.3.0
Fix Version: 1.3-current (r8272)
Test Compiled FLTK with the revised file.
No Sign of the Compilation errors seen before.
Problem Fixed I'd say.
Sorry - Neglected to mention:
FLTK 1.3.0rc3-8207 (current)
gcc 4.4.3
Linux (tinycore 3.4.1)
Valgrind-ing, I believe I found the source of a leak in Fl_x.cxx.
fl_get_font_xfld() malloc's and returns a char * to fl_new_ic(), but the
latter does not free this space. From what I can tell,
On 14.01.2011, at 10:02, Denton Thomas wrote:
Sorry - Neglected to mention:
FLTK 1.3.0rc3-8207 (current)
gcc 4.4.3
Linux (tinycore 3.4.1)
Valgrind-ing, I believe I found the source of a leak in Fl_x.cxx.
fl_get_font_xfld() malloc's and returns a char * to fl_new_ic(), but the
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2522
Version: 1.3.0
The attached patch hides the Fl_X class under WIN32,
to complete the operation already committed for Mac OS and X11.
With the patch, FLTK must be
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
While your looking at this,
All of the dsp files in the ide/VisualC6 folder append $(ProjectName) to
the Output_Dir and Intermediate_Dir definitions.
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
Are you sure you have the latest version of VC6? In your original message
was a warning that Win98 is only supported as a Beta, combined with your
Valgrind-ing, I believe I found the source of a leak in Fl_x.cxx.
fl_get_font_xfld() malloc's and returns a char * to fl_new_ic(), but the
latter does not free this space. From what I can tell, fl_new_ic() needs to
do that.
This seems to solve the problem:
365c365
char *fnt;
---
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
I think I've sorted all the problems now.
I've modified all the .dsp files to replace the $(ProjectName) part of the
path with the individual Project
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
Attached file visualC6_ide_files.zip...
Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
Attachment:
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
BTW, all modified files in the ZIP Archive are dated 14/11/2011
Link: http://www.fltk.org/str.php?L2521
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?L2522
Version: 1.3.0
-1 on using FL_LIBRARY for Windows, i.e. we should change FL_LIBRARY to
another name for this purpose, as discussed in fltk.development, and this
This is a test, no reply necessary.
I want to see where the fltk-b...@fltk.org emails go..
___
fltk-bugs mailing list
fltk-bugs@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-bugs
[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2519
Version: 1.3.0
Fix Version: 1.3-current (r8272)
Closed.
Link: http://www.fltk.org/str.php?L2519
Version: 1.3.0
Fix Version: 1.3-current (r8272)
___
fltk-bugs mailing list
On 14.01.2011, at 01:19, Dmitrij K wrote:
Hi all.
I update of my Linux (Gentoo Linux) (kde-4.4.5, xorg-1.9.2) and I having
now problems in work a fluid2: I can't change some object in the
fluid2-tree or click some a button, so this is doing impossible building
GUI in the fluid2.
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2523
Version: 1.3.0
The following symbols are declared in Fl_PostScript.H but do not seem to
have any definition:
void transformed_draw(const char* s, double x, double
On Linux in the moment, I using a fluid2.exe through an emulator `wine' and
all works OK...
___
fltk-bugs mailing list
fltk-bugs@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-bugs
Author: manolo
Date: 2011-01-14 03:48:18 -0800 (Fri, 14 Jan 2011)
New Revision: 8277
Log:
Fix memory leak in fl_new_ic() reported by Denton Thomas.
Modified:
branches/branch-1.3/src/Fl_x.cxx
Modified: branches/branch-1.3/src/Fl_x.cxx
Perhaps we could also allow defining FL_UNSTABLE or
FL_UNPORTABLE to get the OS-specific definitions then?
Oh yes, I can see that working, +1,
Some sort of FL_low_level_feature_here_be_dragons... option sounds
like a good idea, and we separate the Fl_X stuff from the FL_LIBRARY
option,
There seem to have been quite a few posts direct to fltk.bugs recently
by users unfamiliar with our ways... Some of these even seem to have
been of some merit (so it's good that Matt reads them!)
However, I still wonder why fltk-bugs is not just made read only so
that only the STR stuff goes
Michael Sweet wrote:
Perhaps we could also allow defining FL_UNSTABLE or FL_UNPORTABLE to get the
OS-specific definitions then?
Or FL_OS_SPECIFIC or FL_INTERNALS ?
Yes, something like that maybe.
Albrecht
___
fltk-dev mailing list
MacArthur, Ian (SELEX GALILEO, UK) wrote:
There seem to have been quite a few posts direct to fltk.bugs recently
by users unfamiliar with our ways... Some of these even seem to have
been of some merit (so it's good that Matt reads them!)
However, I still wonder why fltk-bugs is not just made
MacArthur, Ian (SELEX GALILEO, UK) wrote:
Some sort of FL_low_level_feature_here_be_dragons... option sounds
like a good idea, and we separate the Fl_X stuff from the FL_LIBRARY
option, resolving Albrecht's point.
Though if we are doing that, I guess we'd need to do it before 1.3.0
goes
On 13.01.2011, at 21:05, fltk-dev@easysw.com wrote:
Author: manolo
Date: 2011-01-13 12:05:32 -0800 (Thu, 13 Jan 2011)
New Revision: 8273
Log:
Fixed WIN32 crash when printing with the test/mandelbrot demo.
Modified: branches/branch-1.3/src/fl_draw_image_win32.cxx
On 14.01.2011, at 13:19, Albrecht Schlosser wrote:
MacArthur, Ian (SELEX GALILEO, UK) wrote:
There seem to have been quite a few posts direct to fltk.bugs recently
by users unfamiliar with our ways... Some of these even seem to have
been of some merit (so it's good that Matt reads them!)
On 14.01.2011, at 16:18, Albrecht Schlosser wrote:
On 14.01.2011 13:50, Matthias Melcher wrote:
We could also just open it to the public... . This has two advantages:
1. we never have to explain anymore why the user should not post there
2. we not only have a dedicated bugs, area, but
MacArthur, Ian (SELEX GALILEO, UK) wrote:
There seem to have been quite a few posts direct to fltk.bugs recently
by users unfamiliar with our ways... Some of these even seem to have
been of some merit (so it's good that Matt reads them!)
However, I still wonder why fltk-bugs is not just made
On Jan 14, 2011, at 1:59 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
There seem to have been quite a few posts direct to fltk.bugs recently
by users unfamiliar with our ways... Some of these even seem to have
been of some merit (so it's good that Matt reads them!)
However, I still wonder
On Jan 14, 2011, at 7:59 AM, Greg Ercolano wrote:
...
If we change this, 'fltk-b...@fltk.org' needs to be redirected
(eg. to fltk.general), as I think that's possibly where a lot
of the fltk.bugs messages come from.
Recall we have 10 years of FLTK code that said at
Right. One thing you can do is make your application
/borederless/, and then draw the entire window border
and buttons
and behavior yourself.
It will then be up to you to handle making the 'close'
and 'iconify'
buttons as well as window dragging and
However, in digging in to the problem a bit further, I seem to have uncovered
a bag of worms.
After all that, I have found the answer to my problem.
The code creating the Text Editor did not initialise the Text Buffer correctly.
Thanks for your responses and sorry for the noise :-(
Following the resolution of my previous errors, I now get a large (1826) number
of Linker warnings when creating fltk_images.lib
I've raised STR 2521 on this and attached a complete log of the build.
___
fltk mailing list
fltk@easysw.com
Following the resolution of my previous errors, I now get a
large (1826) number of Linker warnings when creating fltk_images.lib
I've raised STR 2521 on this and attached a complete log of the build.
That looks weird - looks like the fltk_jpeg lib somehow incorporates
duplicates of the
Using: fltk-1.3.x-r8276 / Linux 2.6.33.3 (tinycore) on i686 / gcc 4.4.3
Found via Valgrind and a one-button hello program. In Fl_x.cxx, fl_init_xim()
allocates an XIM object using a call to libx11. fl_init_xim() only deallocates
that object in some cases, rather than in all. It looks like the
Well ian you had it right in the first place...i was referring to the
little icon you see in the top left of a windows box, like for
example using internet explorer you see the little 'e' icon in top left.
In SDL there was a function to assign this icon, if i recall it has
two parameters first is
Found via Valgrind and a one-button hello program. In
Fl_x.cxx, fl_init_xim() allocates an XIM object using a call
to libx11. fl_init_xim() only deallocates that object in some
cases, rather than in all. It looks like the object is not
needed after fl_ini_xim(), so it should be
fltk-1.3.x-r8276 / Linux 2.6.33.3 (tinycore) on i686 / gcc 4.4.3
find_best_font() keeps a static pointer to the list of font names provided by
libx11. find_best_font() frees and then re-queries that list from libx11 every
time find_best_font() is run. At program termination, that list cannot be
Hmm, you have turned off XFT in your build, then? You get much nicer
looking text display if you leave XFT enabled in 1.3...
find_best_font() keeps a static pointer to the list of font
names provided by libx11. find_best_font() frees and then
re-queries that list from libx11 every time
Paul R wrote:
Well ian you had it right in the first place...i was referring to the
little icon you see in the top left of a windows box, like for
example using internet explorer you see the little 'e' icon in top left.
...
So i think i should look at the sudoku example you mentioned..
There
Found via Valgrind and a one-button hello program. In=20
Fl_x.cxx, fl_init_xim() allocates an XIM object using a call=20
to libx11. fl_init_xim() only deallocates that object in some=20
cases, rather than in all. It looks like the object is not=20
needed after fl_ini_xim(), so it should
Hmm, you have turned off XFT in your build, then? You get much nicer
looking text display if you leave XFT enabled in 1.3...
find_best_font() keeps a static pointer to the list of font=20
names provided by libx11. find_best_font() frees and then=20
re-queries that list from libx11 every
So i think i should look at the sudoku example you mentioned..
There is also a (short) description in the OS Issues chapter of the
docs.
Albrecht
This is resolved.. a really rather painless too!
After looking at the docs and seeing an implementation in sudoku i have
this:
relevant lines
Yep, I go to/from the XFT. Sometimes the hard lines are
refreshing to look at, but XFT is much better for production.
OK - I favour XFT across the board... Once you have to start rendering
non-ASCII text, well, XFT handles those fonts better...
Re the would-be-patch, thanks for the details.
Ian wrote
That looks weird - looks like the fltk_jpeg lib somehow incorporates
duplicates of the entire fltk.lib...
Must be a linker misconfig or something, I guess?
Looks like you were right Ian,
I think I've sorted all the problems now.
I've modified all the .dsp files to replace the
On 14.01.2011 14:55, Brian Tilley wrote:
Ian wrote
That looks weird - looks like the fltk_jpeg lib somehow incorporates
duplicates of the entire fltk.lib...
Must be a linker misconfig or something, I guess?
Looks like you were right Ian,
I think I've sorted all the problems now.
I've
hi all,
I have decided again to try and add the help dialog but cannot build
I add the couple of lines of code and the header straight into
main, i had built proj ok adding the images library a couple of minutes
before,(without help dialog) but then i added the lines for the
help dialog and it
presently i am using png.a, fltk.a, images.a, _z.a
i added the jpeg library and now only get a few errors about
undefined reference to inflate init_
it seems i am going to have to use a lot of libraries to get this
helpdlg going
___
fltk mailing
Well here is an excerpt from the log now
it is 14 errors in total, all almost the same..all about png and i have
added every library now..so it is linking order or something??
.\fltk13rc2\lib\libfltk_png.a(pngread.o):pngread.c|| undefined reference to
`inflateInit_'|
Paul R wrote:
undefined reference to png_create, read_struct
undefined reference to jpeg std error
undefined reference to jpeg finish decompress
etc
I had been advised to add the fltk library 'before' fltk.a so i did
this, same problems
i added the fltk_z.a library as i thought that was
Paul R wrote:
Well here is an excerpt from the log now
it is 14 errors in total, all almost the same..all about png and i have
added every library now..so it is linking order or something??
.\fltk13rc2\lib\libfltk_png.a(pngread.o):pngread.c|| undefined reference to
`inflateInit_'|
Greg Ercolano wrote:
Paul R wrote:
Well here is an excerpt from the log now
it is 14 errors in total, all almost the same..all about png and i have
added every library now..so it is linking order or something??
.\fltk13rc2\lib\libfltk_png.a(pngread.o):pngread.c|| undefined reference to
On 14.01.2011 20:40, Matthias Melcher wrote:
lbfltk_png is just the interface between fltk and png, You still have to link
with libpng. png then again depends on zlib, so you have to link that as
well. And while you are at it, ling libjpeg as well.
libfltk_png *is* libpng, if you use the
On 14.01.2011, at 20:51, Albrecht Schlosser wrote:
On 14.01.2011 20:40, Matthias Melcher wrote:
lbfltk_png is just the interface between fltk and png, You still have to
link with libpng. png then again depends on zlib, so you have to link that
as well. And while you are at it, ling
On 14/01/11 16:46, Paul R wrote:
hi all,
I have decided again to try and add the help dialog but cannot build
Did the example I posted not work for you? Worked OK for me...
___
fltk mailing list
fltk@easysw.com
On 14/01/11 13:22, Denton Thomas wrote:
Agreed, setting to NULL at declaration is pointless! Line 546 is
fine.
Also agreed that it is smart to check xim_styles before use, and to
set it to NULL after. The xlib doc does not specify whether XFree
will or won't set incoming values to NULL.
54 matches
Mail list logo
