DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2529
Version: 1.3-current
With the new functionality to read png image frommemory there is a compiler
warning about fp can be used without initialization the patch
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2530
Version: 1.3-current
You can reproduce this by editing test/editor.cxx to uncomment
w-editor-wrap_mode (incidentally, I think the second argument, 250, is
ignored
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2531
Version: 1.3-current
To reproduce, create a small text file where each line begins with '//',
which makes the editor make them proportional. Then run test/editor on
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2531
Version: 1.3-current
Yes, the problem is, that FLTK used to use integers as character widths,
but OS X requires floats. Not all of the code has been ported to use
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2530
Version: 1.3-current
Yes. In order to calculate word wrapping, Fl_Text_Display runs up and down
the string, calculating its width sometimes on a per-character base.
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
Great -- I had the flu last weekend, so I was out of it, couldn't look into
this.
But I'll try to get back on it and check it in once carefully
Author: matt
Date: 2011-01-19 15:14:09 -0800 (Wed, 19 Jan 2011)
New Revision: 8292
Log:
Fluid binary type adds size to the array of unsigned char, giving better access
to the resource.
Modified:
branches/branch-1.3/fluid/Fl_Function_Type.cxx
Modified:
Author: AlbrechtS
Date: 2011-01-19 16:37:18 -0800 (Wed, 19 Jan 2011)
New Revision: 8293
Log:
Updated VisualC2008 and VisualC2010 project files to define FL_LIBRARY in
non-dll builds. Also changed some dependencies to get correct build order.
To Do: VisualC2008 doesn't create the .cxx and .h files
On 19.01.2011 00:04, Domingo Alvarez Duarte wrote:
With the latest svn update there is a problem with this new macro
FL_INTERNALS I think.
When compiling fluid there is a problem:
Compiling CodeEditor.cxx...
In file included from ../FL/fl_draw.H:39:0,
from ../FL/Fl_Text_Display.H:36,
from
When compiling fluid there is a problem:
Compiling CodeEditor.cxx...
In file included from ../FL/fl_draw.H:39:0,
from ../FL/Fl_Text_Display.H:36,
from ../FL/Fl_Text_Editor.H:37,
from CodeEditor.h:41,
from CodeEditor.cxx:36:
../FL/Fl_Device.H:331:3: error: 'XPoint' does not name
After your questions I've created a fresh fltk copy and compiled and it
work's fine, I'm looking at my old copy to see what I've messed.
Thanks for your questions !
___
fltk-dev mailing list
fltk-dev@easysw.com
I've found the problem, I did modified Fl_Graphics_Driver to use member
variables instead of static variables for all matrix manipulation and for
that I need the declaration of XPOINT to be visible, this modifi8action
was needed to implement Fl_PDF_Driver, because I need to switch betwen
Here is my diff for fl_draw.h using Fl_Graphics_Driver member methods
instead of using static variables.
fl_draw-without-static-variables.diff
Description: Binary data
___
fltk-dev mailing list
fltk-dev@easysw.com
Replying to 2 messages at once:
On 19.01.2011 13:01, Domingo Alvarez Duarte wrote:
I've found the problem, I did modified Fl_Graphics_Driver to use member
variables instead of static variables for all matrix manipulation and
for that I need the declaration of XPOINT to be visible, this
I think when the release goes out there should be a warning about
Fl_Text_Display slowness. After all, it means that any app that uses
it for more than 50 lines or so is effectively no longer portable to
OS X (yes, it really is that slow... it wedges for about 5s to
sequentially add 50 lines, and
Evan Laforge wrote:
I thought I made a STR for these things, but I don't see it anymore.
Should I add one? Or one STR for each issue?
Just regarding this: I went to http://fltk.org/str.php and searched
for elaforge and found only these items:
Id PriorityStatus
REsearching the exception problem I'm facing wint win32 I decided to test
with vc++ 2008 express and for my surprise I'm getting the following
errors on a fresh svn checkout.
g:\tmp\c\fltk-svn-raw\fl\win32.H(106) : error C4430: missing type
specifier - int assumed. Note: C++ does not
It seems that the supplied ide/projects aren't updated to include
FL_INTERNAL of FL_LIBRARY, because defining one of then make it works.
___
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
Casually on executing test/pixmap_browser I discover that when pressing
load button and canceling the application segfault.
___
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
In my research for the exception problem I compiled a test program with
vc++ 2008 express and it works as expected, the same program doesn't work
as expected when compiled with mingw, so i'm trying it with andLinux and
the same fresh fltk svn doesn't compile on it:
Compiling Fl.cxx...
On Wed, Jan 19, 2011 at 9:59 AM, Greg Ercolano e...@seriss.com wrote:
Evan Laforge wrote:
I thought I made a STR for these things, but I don't see it anymore.
Should I add one? Or one STR for each issue?
Just regarding this: I went to http://fltk.org/str.php and searched
for
On 19.01.2011 22:33, Domingo Alvarez Duarte wrote:
It seems that the supplied ide/projects aren't updated to include
FL_INTERNAL of FL_LIBRARY, because defining one of then make it works.
Thanks, I thought that they had it already (grep found some hits), but
I didn't verify.
I'm going to
After editing the bad generated config.h on andLinux the same exception
test program used with vc++ 2008 express and mingw was compiled and
excuted and worked as expected so the problem is with the mingw compiler.
___
fltk-dev mailing list
Evan Laforge wrote:
Hm, maybe I didn't add a STR back then after all. Ok, I'm going to
add STRs for slowness, incorrect wrapping, and text wobble, along
with an example program that demonstrates it. I'll add them for 1.3,
since they are after all serious bugs, but if consensus is push them
On 19.01.2011 22:33, Domingo Alvarez Duarte wrote:
It seems that the supplied ide/projects aren't updated to include
FL_INTERNAL of FL_LIBRARY, because defining one of then make it works.
This should be solved now in svn r 8293, although there are still
some problems with generation of .cxx and
I'm trying to handle exceptions on a fltk application under win32 and
compiled with mingw 4.5.2 but it seems that the exceptions doesn't reach
the main function, the program allways terminate without the exception
been caught.
Someone else succeed catching exceptions or have a good strategy
yes i care about it, i want to create a robust, quality
appliction, and thanks to the support on these pages i have
come a long way in the past 6 months or so. I need to review
the docs in depth regarding the show(argc, argv) because i
cannot understand where all the switch parameters
I have trouble setting VC++ 6.0. I followed the compiling programs with
microsoft visual c++ to run hello.cxx sample program, from this link:
http://www.fltk.org/doc-1.0/basics.html, but I am not sucessful in setting up
the working environment.
It says:
In Visual C++ you will need to tell the
I'm trying to handle exceptions on a fltk application under win32 and
compiled with mingw 4.5.2 but it seems that the exceptions doesn't reach
the main function, the program allways terminate without the exception
been caught.
Someone else succeed catching exceptions or have a good strategy
The issue on win32 with mingw is in some way the cross shared libraries
exception problem, I installed a try {} catch(...){} inside Fl::handle and
it catches my exceptions there.
It seems that in some way we need to have an option to override Fl::handle
to catch exceptions before pass
I did modified the Fl class to allow overwrite Fl::handle and now I can
catch any non managed exception on the override Fl:handle, but I'm getting
zombie windows when an exception is caught.
Fl.H
...
/** signature of main event handler */
typedef int (*Fl_Main_Event_Handler)(int e,
Hi all,
I have a Fl_Group upon which a Grid is drawn.
By pressing a button a simple red rectangular Fl_Widget (box: FL_FLAT_BOX) is
added to the Fl_Group, then the draw-method of the Fl_Widget is called.
I expected to see a solid red area - but the Grid is shining through the
rectangular
testalucida wrote:
Hi all,
I have a Fl_Group upon which a Grid is drawn.
By pressing a button a simple red rectangular Fl_Widget (box: FL_FLAT_BOX) is
added to the Fl_Group, then the draw-method of the Fl_Widget is called.
I expected to see a solid red area - but the Grid is shining
On 19.01.2011 19:57, Giau P wrote:
I have trouble setting VC++ 6.0.
VC++ 6.0 is really old. We're only partly supporting this for
compatibility. If you can, you should use VC++ 2008 or later.
I followed the compiling programs with microsoft visual c++ to run
hello.cxx sample program, from
Albrecht Schlosser wrote:
On 19.01.2011 19:57, Giau P wrote:
I have trouble setting VC++ 6.0.
VC++ 6.0 is really old. We're only partly supporting this for
compatibility. If you can, you should use VC++ 2008 or later.
Agreed.
I followed the compiling programs with microsoft visual
testalucida schrieb:
Hi all,
I have a Fl_Group upon which a Grid is drawn. By pressing a button a
simple red rectangular Fl_Widget (box: FL_FLAT_BOX) is added to the
Fl_Group, then the draw-method of the Fl_Widget is called. I expected
to see a solid red area - but the Grid is shining
Hi Greg, thanks for your answer.
Actually I used a class derived from Fl_Widget with it's own draw method.
Now I changed the base class to Fl_Box and took the draw method off my derived
class so as to use Fl_Box' method.
The problem remains the same: the grid is shining through (or is drawn above
37 matches
Mail list logo
