manolo gouy wrote:
Albrecht: I have here a little lift to give to your morale :=)
Thanks, but my morale is okay. ;-)
The print demo no longer loose widgets, because
I removed a clip to window that works well (and is useful) under Mac
but made all these widgets disappear in the print demo
Hello everyone !
I have a very simple question. Do you plan to use more C++ features in the
future for FLTK? Like std::string, functors, STL, etc... If you use many of C++
strengths, I am sure that the library will still be very light, and even more
pleasant to use.
Thanks !
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2310
Version: 1.3-feature
I believe to have sorted out the clipping problem under MSWindows.
Update file src/fl_rect.cxx from the last svn for that.
I tried these demos
On 14 Feb 2010, at 11:04, Dufour wrote:
I have a very simple question. Do you plan to use more C++ features
in the future for FLTK? Like std::string, functors, STL, etc...
This question, or some similar variant of it, comes up every now and
then - so far the answer has always been; well,
On 14 Feb 2010, at 1:18, Evan Laforge wrote:
So from looking around in Fl_cocoa.mm I couldn't help but notice fltk
has this whole complicated system for handling non-ascii text input
that seems to be incompatible with the system provided one. That
probably made sense for X which has (or
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2310
Version: 1.3-feature
Rewrote Fl_Printer::print_widget() so it uses as_group() and as_window()
to traverse the widget tree looking for subwindows.
Link:
[..] - note that many of the C++ features people ask for
- e.g. std::string, STL, etc... - are not part of the language
definition per se, they are part of the surrounding infrastructure
around the language core
Ian, I don't want to be adversarial, nor do I want to engage
in a debate about
Using fltk-1.3, on linux and win32 systems, when I want to input
Japanese or Chinese text, for example, I invoke the host system's IME
and enter text in that.
The IME then sends the composed UTF8 sequences to the foreground
(fltk) window and all seems to be well.
Fltk's own, historical,
Of course, you can use any or all of these extensions with fltk in
your own code; indeed I often use STL containers for managing lists
of items and widgets these days myself, though I have had issues with
the differences in STL implementations between linux and win32, for
example. [...]
As I
On 14 Feb 2010, at 16:07, s...@sjssoftware.com wrote:
Ian, I don't want to be adversarial,
It's OK - I respect your input; I've seen plenty of stuff from you to
know that you know your stuff, and value your opinions: Tell me I'm
wrong and I'll believe you!
Use it or don't, but thinking
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2310
Version: 1.3-feature
I have (correctly this time I believe) changed the MSWindows
version of Fl_Printer so the default origin of graphics coordinates
is at top left
On 14 Feb 2010, at 18:02, Evan Laforge wrote:
Fltk's own, historical, compose key mechanism does not seem to me to
be involved (indeed I suspect that mainly handles the typing of LGC
glyphs that don't appear on a your keyboard, e.g. me typing ß on a UK
keyboard that has no key for it...)
ÂCan you show me some of your work, using FLTK with some modern C++? Just
so as I know how to do that.
The templates belong to the modern C++, aren't ? ;-)
For example, I use them to create highlighted buttons:
templateclass T class Fl_Simple_Highlight : public T
{
public:
Hmm, well if that's true, isn't it all redundant and can be removed
right now?
I don't know.
Possibly it can be, or can be made X11 specific - if we believe the
OSX and win32 implementations cover what's needed.
Even if by some chance the fltk input has some great feature that was
awkward
ÂCan you show me some of your work, using FLTK with some modern C++?
Just so as I know how to do that.
The templates belong to the modern C++, aren't ? ;-)
For example, I use them to create highlighted buttons:
templateclass T class Fl_Simple_Highlight : public T
{
public:
Dufour wrote:
Hello everyone !
I have a very simple question. Do you plan to use more C++ features in the
future for FLTK? Like std::string, functors, STL, etc... If you use many of
C++ strengths, I am sure that the library will still be very light, and even
more pleasant 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?L2310
Version: 1.3-feature
Clipping: works much better now, thanks for finding this annoying bug.
:-) :-) :-)
test/unittests - viewport test, however, shows the
I modern c++ features in my programs which use fltk, but I don't
think fltk is actually hurt that much by not using them itself. Yes,
Fl_Group could use std::vector, but that code is there and debugged
and it's not too complicated to deal with the children array on your
own. It could use
Contato: pcnetsecur...@gmail.com
Contato: pcnetsecurity @ gmail.com
Planos a partir de R$ 250,00 .
Assistência Técnica
Prestamos assistência técnica nos computadores de sua empresa ou residência, e
também possuímos uma equipe qualificada para fazer a manutenção no próprio
local.
-
I'll see whether there is some missing update of the event_x_root()
value in the present code.
Thank for fixing this!
About the doc: may be its intent is to provide a procedure that works
on subwindows as well as on windows. I agree it's more
intuitive to just do window-x() to get window's
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2310
Version: 1.3-feature
I added compatibility functions for Linux/X11 so that it compiles, but
doesn't do anything useful (except a warning message), updated the
21 matches
Mail list logo
