On 18.01.2011 06:15, Ish wrote:
undefined reference to `Fl::gl_visual(int, int*)'
I believe that error means its implementation is missing. I haven't checked
the source yet to confirm that. It isn't virtual from what I understand in
the source code.
using Fltk 1.3
Which exakt FLTK
On 18.01.2011 09:59, Albrecht Schlosser wrote:
On 18.01.2011 06:15, Ish wrote:
undefined reference to `Fl::gl_visual(int, int*)'
I believe that error means its implementation is missing. I haven't
checked the source yet to confirm that. It isn't virtual from what I
understand in the
On 18.01.2011 09:59, Albrecht Schlosser wrote:
On 18.01.2011 06:15, Ish wrote:
undefined reference to `Fl::gl_visual(int, int*)'
I believe that error means its implementation is missing. I haven't
checked the source yet to confirm that. It isn't virtual from what I
understand
On 18.01.2011, at 15:55, Ish wrote:
On 18.01.2011 09:59, Albrecht Schlosser wrote:
On 18.01.2011 06:15, Ish wrote:
undefined reference to `Fl::gl_visual(int, int*)'
I believe that error means its implementation is missing. I haven't
checked the source yet to confirm that. It isn't virtual
[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2528
Version: 1.1.10
Fix Version: None
This is correct. Fl_Tooltip is a purely static class. There is no need for
a constructor because you can not instantiate it. To add a tooltip to a
widget, simply call
myWidget-tooltip(Wssn
On 15.01.2011, at 10:11, kdi...@live.ru wrote:
On Linux in the moment, I using a fluid2.exe through an emulator `wine' and
all works OK...
Sorry, I don't know how to help you. Please try again in the fltk.general
mailing list.
___
fltk-bugs
On 18.01.2011, at 15:55, Ish wrote:
On 18.01.2011 09:59, Albrecht Schlosser wrote:
On 18.01.2011 06:15, Ish wrote:
undefined reference to `Fl::gl_visual(int, int*)'
=20
I believe that error means its implementation is missing. I =
haven't
checked the source yet to confirm that. It
Author: manolo
Date: 2011-01-18 22:29:06 -0800 (Tue, 18 Jan 2011)
New Revision: 8290
Log:
Removed compiler warning:
Fl_PNG_Image.cxx:108: warning: 'fp' may be used uninitialized in this function
Modified:
branches/branch-1.3/src/Fl_PNG_Image.cxx
Modified:
Author: manolo
Date: 2011-01-18 22:33:48 -0800 (Tue, 18 Jan 2011)
New Revision: 8291
Log:
Removed gcc 4.4 compiler warning:
Fl_Preferences.cxx:1322: warning: ignoring return value of
?\226?\128?\152size_t fwrite(const void*, size_t, size_t,
FILE*)?\226?\128?\153, declared with attribute
This'll depend on what headers you have installed for glibc I guess, but
I doubt we can get rid of all the declared with attribute
warn_unused_result warnings unless we either alter the code, or maybe
there's some compiler option to tell gcc to just shut up about them?
Most of them are just
This'll depend on what headers you have installed for glibc I guess, but
I doubt we can get rid of all the declared with attribute
warn_unused_result warnings unless we either alter the code, or maybe
there's some compiler option to tell gcc to just shut up about them?
Most of them are just
-Wno-unused-result is the GCC option you are looking for...
On Jan 18, 2011, at 3:03 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
This'll depend on what headers you have installed for glibc I guess, but
I doubt we can get rid of all the declared with attribute
warn_unused_result warnings
On 14.01.2011, at 18:38, Michael Sweet wrote:
I can certainly make fltk.bugs/fltk-bugs read-only. It'll mean some changes in
the bug system too (emails to fltk-bugs would need to be posted to fltk.bugs
directly, for example) but nothing we can't handle.
Mike, we've got at least three positive
On 18.01.2011, at 19:14, Albrecht Schlosser wrote:
On 14.01.2011, at 18:38, Michael Sweet wrote:
I can certainly make fltk.bugs/fltk-bugs read-only. It'll mean some changes
in
the bug system too (emails to fltk-bugs would need to be posted to fltk.bugs
directly, for example) but nothing
On Jan 18, 2011, at 10:14 AM, Albrecht Schlosser wrote:
On 14.01.2011, at 18:38, Michael Sweet wrote:
I can certainly make fltk.bugs/fltk-bugs read-only. It'll mean some changes
in
the bug system too (emails to fltk-bugs would need to be posted to fltk.bugs
directly, for example) but
Yuri P. Fedorchenko wrote:
I want to tell that not all warning are needed to suppress.
I think that for examle commit [Library] r8275 - branches/branch-1.3/FL
seams
strange for me
one of changes.
- virtual const char *item_text(void *item) const { return 0L; }
+ virtual const char
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
Hi all,
I am experiencing the problem described in article:
http://www.fltk.org/articles.php?L744
you can see a screen of the actual error here:
http://img249.imageshack.us/i/iconerror.png/
i am developing for windows only and have tested on 2000,xp,7
same problem occurs with all.
on double
On reflection i think this is the first time i have tested the
'double click file to startup' since i built with rc2 so that is
probably why i thought it was to do with the new icon. With fltk 1.3xx
that i used previously, the problem did not occur.
I just realised, this error is occuring
i tried the easiest thing first and removed (argv, argc) from the
call to mainWin-show(); the icons for the window still display fine???
And my original problem has gone away, so leaving it at that!
so i am just wondering why the
docs were saying icons would not display unless -show(argc, argv)
In the docs for 1.3
http://www.fltk.org/doc-1.3/index.html
I found the function:
FL_Window::Icon
which i implement as
mainWin-icon((char* )LoadIcon(fl_display, MAKEINTRESOURCE(IDI_ICON)));
And the note at the end of the docs section:
You must call Fl_Window::show(int argc, char** argv) for
Hi all,
I am experiencing the problem described in article:
http://www.fltk.org/articles.php?L744
you can see a screen of the actual error here:
http://img249.imageshack.us/i/iconerror.png/
i am developing for windows only and have tested on 2000,xp,7
same problem occurs with all.
on
So how come it is working ok? Or is this something that has yet to be
updated in the docs?
Luck.
Or is it something that cannot be relied on
unless the show(int argc, char** argv) method is used?
Yes, the later - different host OS variants behave differently. If it
works for you on your
ivansc schrieb:
I'm trying to write an application that puts a control window on the
first screen, and a full-screen display on the second screen.
Is there something straightforward that I've overlooked?
AFAIK for windows there is no first or second screen, but only a common
desktop
So how come it is working ok? Or is this something that has yet to be
updated in the docs?=20
Luck.
Or is it something that cannot be relied on
unless the show(int argc, char** argv) method is used?
Yes, the later - different host OS variants behave differently. If it
works for you
On 18.01.2011, at 15:14, Paul R wrote:
The program only runs from args when a file is double clicked or if the user
know about such things 'dragged and dropped' onto the exe,
both of which things result in argc = 2, any higher and i have fails in
place, argc = 1 is ignored as i am using the
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 are being
On 18.01.2011, at 17:11, Albrecht Schlosser wrote:
On 18.01.2011, at 15:14, Paul R wrote:
The program only runs from args when a file is double clicked or if the user
know about such things 'dragged and dropped' onto the exe,
both of which things result in argc = 2, any higher and i have
On 18.01.2011, at 18:40, Paul Rogan wrote:
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
But this only works, when additional screen is placed to right top side
of first screen. When the second screen is placed different (maybe on
top of first screen) the offset changes.
I've run my test code on Mac OS X, Windows, and Linux. I've found 2 things.
Positioning windows onto the
Hi guys I am making a very simple graph widget. It has a window for a graph
constructed by iterating through a vector of points and calling fl_line on two
consecutive points.
Additionally I have a text that indicates the coordinate i am pointed at and a
cross that comes from the sides of the
On 18/01/11 22:16, Ish wrote:
Hi guys I am making a very simple graph widget. It has a window for a
graph constructed by iterating through a vector of points and calling
fl_line on two consecutive points.
Additionally I have a text that indicates the coordinate i am pointed
at and a cross
Ish wrote:
Can you give me any advice on how to do this properly?
One way would maybe be to use overlays to draw the cursor.
Assuming the hardware supports it, this would let you draw and clear
the cursor without affecting the image underneath.
Example code here:
33 matches
Mail list logo
