On 12/10/2011 07:59 AM, Albrecht Schlosser wrote:
Anyway, if we did this, code that still resizes widgets in their
draw() methods would probably still work as before, but widgets
using the new layout() (or whatever it's called) method would
benefit from the new features. At least that's what
On 09.12.2011 21:36, Bill Spitzak wrote:
On 12/08/2011 09:47 AM, Matthias Melcher wrote:
There is something similar in FLTK 2. It has a virtual function named
layout() that adjusts widgets sizes and available space. I am
planning on using the layout mechanism in 3 - unless of course there
is
On 12/10/2011 06:08 AM, Albrecht Schlosser wrote:
But there is a *massive* problem, if widgets are allowed to resize
themselves in the draw() method, as it is now in FLTK 1. Widgets that
have problems with this are at least Fl_Pack, to some extent also all
widgets that allow scrollbars to
On 10.12.2011 16:26, Bill Spitzak wrote:
On 12/10/2011 06:08 AM, Albrecht Schlosser wrote:
But there is a *massive* problem, if widgets are allowed to resize
themselves in the draw() method, as it is now in FLTK 1. Widgets that
have problems with this are at least Fl_Pack, to some extent also
On 12/08/2011 09:47 AM, Matthias Melcher wrote:
There is something similar in FLTK 2. It has a virtual function named
layout() that adjusts widgets sizes and available space. I am planning on
using the layout mechanism in 3 - unless of course there is abetter way?!
This is not working in
There is something similar in FLTK 2. It has a virtual function named
layout() that adjusts widgets sizes and available space. I am planning on
using the layout mechanism in 3 - unless of course there is abetter way?!
On 01.12.2011, at 07:17, Lynn Quam wrote:
I am a new user of FLTK3 who is
Have yoy looked at the EvaLayout that I managed to make it work with fltk ?
http://www.fltk.org/str.php?L2785+P0+S-2+C0+I0+E0+Qevalayout
On Thu, 08 Dec 2011 18:47:28 +0100, Matthias Melcher m...@matthiasm.com
wrote:
There is something similar in FLTK 2. It has a virtual function named
On 02.12.2011 11:10, MacArthur, Ian (SELEX GALILEO, UK) wrote:
Huh? I don't understand the question.
You get the size of a button just by calling its w() and
h() methods.
What property of the widget are you trying to measure other than its
width and height?
The w() and h() methods return
I am a new user of FLTK3 who is migrating from using Tcl/Tk
for GUI development. My software development is in Common
Lisp (SBCL). I have some tests successfully running using
FLTK3 in combination with OpenGL.
Maybe a bit premature for fltk3 - expect a lot of change before we put
it
I was looking for a layout manager too and although I didn't
found/implemented one that satisfy me I found several things close/related
to this problem:
-Evalayout an interesting solution that would be nice to have on FLTK:
http://www.codeproject.com/KB/dialog/EvaLayout.aspx
-SPTk New Layout
Huh? I don't understand the question.
You get the size of a button just by calling its w() and h() methods.
What property of the widget are you trying to measure other than its
width and height?
The w() and h() methods return the size that the user requested when the widget
was created or
I am a new user of FLTK3 who is migrating from using Tcl/Tk for GUI
development. My software development is in Common Lisp (SBCL). I have some
tests successfully running using FLTK3 in combination with OpenGL.
I like everything I am seeing in FLTK3, EXCEPT for (semi-)automatic layout of
12 matches
Mail list logo
