[fltk.general] fltk 1.3.x + cairo -- neato
Someone was asking me about drawing smooth (antialiased) lines in FLTK, and decided to try out FLTK with Cairo support. I was surprised it only took minutes to install + rebuild fltk against it on linux, and it built a working "test/cairo_test" program. The binary for cairo_test is surprisingly small (392k); unless the DLLs it loads are large, I'd say that ain't bloated at all. For those that haven't tread the path, here's some breadcrumbs; o There's a test/cairo_test program to test fltk+cairo o Assuming the cairo development libs are installed (the single command 'yum install cairo-devel' in my case) you just need to rebuild fltk with "configure --enable-cairo" o Once rebuilt, the test/cairo_test program should show a rendering that uses the cairo library (gradients, smooth antialiased lines, etc) Only had one small link hitch; apparently the link flag "-lpixman-1" in the FLTK Makefile is no longer needed. Here's how I went from just fltk to fltk+cairo on centos 5.5: yum install cairo-devel ..then to rebuild fltk: cd /usr/local/src/fltk-1.3.x-svn make distclean ./configure --enable-cairo make I got this small error during the build of cairo_test: [..] Linking cairo_test... /usr/bin/ld: cannot find -lpixman-1 collect2: ld returned 1 exit status make[1]: *** [cairo_test] Error 1 ..but this was solved by changing this line in the Makefile: -CAIROLIBS = -lcairo -lpixman-1 +CAIROLIBS = -lcairo ..as apparently -lpixman is no longer needed. Another 'make' and fltk built the rest of the way, no errors, and the test/cairo_test program ran OK. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Problems with hide and show
On 8 Dec 2011, at 19:55, David Allen wrote: > I want to have several groups in the same region with all but one hidden at > any one time. It would be like a Wizard except that the order of display is > not sequential. > > Starting with just two groups with no hides, the program compiles and runs. > Because the labels are outside the enclosed widgets, I can tell that both > groups are there. When I attempt to hide one of the groups, g++ gives the > message: > > /usr/local/include/FL/Fl_Widget.H:684: error: ‘virtual void > Fl_Widget::hide()’ is inaccessible > Control/main.cpp:56: error: within this context > Control/main.cpp:56: error: ‘Fl_Widget’ is not an accessible base of > ‘SelectData’ > > I am using 1.3.0. Suggestions would be appreciated. You'll maybe need to show us some code... What you are doing (trying to do) ought to Just Work. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Problems with hide and show
>
> On 08.12.2011, at 20:55, David Allen wrote:
>
> > I want to have several groups in the same region with all but one =
> hidden at any one time. It would be like a Wizard except that the order =
> of display is not sequential.
> >=20
> > Starting with just two groups with no hides, the program compiles and =
> runs. Because the labels are outside the enclosed widgets, I can tell =
> that both groups are there. When I attempt to hide one of the groups, =
> g++ gives the message:
> >=20
> > /usr/local/include/FL/Fl_Widget.H:684: error: =91virtual void =
> Fl_Widget::hide()=92 is inaccessible
> > Control/main.cpp:56: error: within this context
> > Control/main.cpp:56: error: =91Fl_Widget=92 is not an accessible base =
> of =91SelectData=92
> >=20
> > I am using 1.3.0. Suggestions would be appreciated.
>
> You probably wrote=20
>
> class SelectData : Fl_Group {
> ...
> };
>
> which makes Fl_Group a private superclass.
>
> It should be
>
> class SelectData : public Fl_Group {
>
>
>
Yes! Thank you so much.
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Fl_Preferences (bug)
On 08.12.2011, at 21:20, Richard Sanders wrote:
> On Thu, 08 Dec 2011 08:26:54 -0800, Matthias Melcher
> wrote:
>
>> On 30.11.2011, at 23:43, Richard Sanders wrote:
>>
>>> for(loop = 0; loop < entries; ++loop)
>>> {
>>> sprintf(name, "%d", loop);
>>> if(!preference->entryExists(name))
>>> exit(2); // should not get to this but loop will have a value of
>>> 15 at this point
>>
>> Well, you are looking for an entry that is named "15", but that is not in
>> your list.
>
> No kidding. You nailed the problem. When I use the value returned by
> Fl_Preference::entries(); as the loop condition.
> If comment lines are removed then everything works correctly.
> Unfortunately I really need comment lines in the prefs file.
> So the problem is that Fl_Preference::entries(); returns the number of
> entries plus the number of comments.
>
> I would point out that the code I supplied was to demonstrate the
> problem. I was not asking why it did not work, I already know why.
>
> 1) Fl_Preference::entries(); is not fit for purpose as stated in the
> docs.
> 2) Fl_Preference::entries(); is working correctly but the docs give
> erroneous information.
>
> One I think because if two is true then why bother with the function
> in the first place.
I find the documentation precise and correct, but then again, I am not a native
English speaker. Maybe you have a better suggestion what the text should be.
entries() gives the number of entries in a group. The confusing part may be,
that an empty line or a comment line are entries, too (or you could not access
them). The former has an empty name and an empty value. The latter one has no
value, and the comment is the name itself, starting with a semicolon.
So entry(int index) correctly returns the entry at a specific index, which
could also be a comment.
And get(const char *name) returns the entry with a specific name (which in your
case happen to be numbers). There is no mention that numerical names are
counted by entries().
So here are three solution to your problem:
1: add another entry, name "nValues" or "maxID" to know how many ID's you want
to read, or
2: just use get(str, value, "EOD"); . If there is no entry by the name in
'str', value will be "EOD", and you will know that there is no entry by that
name.
3: loop through all entries, but use only those whose name are numerical.
- Matthias
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Problems with hide and show
On 08.12.2011, at 20:55, David Allen wrote:
> I want to have several groups in the same region with all but one hidden at
> any one time. It would be like a Wizard except that the order of display is
> not sequential.
>
> Starting with just two groups with no hides, the program compiles and runs.
> Because the labels are outside the enclosed widgets, I can tell that both
> groups are there. When I attempt to hide one of the groups, g++ gives the
> message:
>
> /usr/local/include/FL/Fl_Widget.H:684: error: ‘virtual void
> Fl_Widget::hide()’ is inaccessible
> Control/main.cpp:56: error: within this context
> Control/main.cpp:56: error: ‘Fl_Widget’ is not an accessible base of
> ‘SelectData’
>
> I am using 1.3.0. Suggestions would be appreciated.
You probably wrote
class SelectData : Fl_Group {
...
};
which makes Fl_Group a private superclass.
It should be
class SelectData : public Fl_Group {
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Fl_Preferences (bug)
On Thu, 08 Dec 2011 08:26:54 -0800, Matthias Melcher
wrote:
>
>On 30.11.2011, at 23:43, Richard Sanders wrote:
>
>> for(loop = 0; loop < entries; ++loop)
>> {
>> sprintf(name, "%d", loop);
>>if(!preference->entryExists(name))
>> exit(2); // should not get to this but loop will have a value of
>> 15 at this point
>
>Well, you are looking for an entry that is named "15", but that is not in your
>list.
No kidding. You nailed the problem. When I use the value returned by
Fl_Preference::entries(); as the loop condition.
If comment lines are removed then everything works correctly.
Unfortunately I really need comment lines in the prefs file.
So the problem is that Fl_Preference::entries(); returns the number of
entries plus the number of comments.
I would point out that the code I supplied was to demonstrate the
problem. I was not asking why it did not work, I already know why.
1) Fl_Preference::entries(); is not fit for purpose as stated in the
docs.
2) Fl_Preference::entries(); is working correctly but the docs give
erroneous information.
One I think because if two is true then why bother with the function
in the first place.
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
[fltk.general] Problems with hide and show
I want to have several groups in the same region with all but one hidden at any one time. It would be like a Wizard except that the order of display is not sequential. Starting with just two groups with no hides, the program compiles and runs. Because the labels are outside the enclosed widgets, I can tell that both groups are there. When I attempt to hide one of the groups, g++ gives the message: /usr/local/include/FL/Fl_Widget.H:684: error: âvirtual void Fl_Widget::hide()â is inaccessible Control/main.cpp:56: error: within this context Control/main.cpp:56: error: âFl_Widgetâ is not an accessible base of âSelectDataâ I am using 1.3.0. Suggestions would be appreciated. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Fl_Preferences (bug)
On 30.11.2011, at 23:43, Richard Sanders wrote:
> for(loop = 0; loop < entries; ++loop)
> {
> sprintf(name, "%d", loop);
>if(!preference->entryExists(name))
> exit(2); // should not get to this but loop will have a value of
> 15 at this point
Well, you are looking for an entry that is named "15", but that is not in your
list. You could be checking for an entry named "duck", and you won't find that
either. This is the API to look for entries by name.
The API to look for entries by index is Fl_Preferences::entry(int ix); which
then corresponds to Fl_Preferences::entries(); . An annotation in an
FL_Preferences database is the same as an entry with a name (the annotation
itself), but no value.
Fl_Preferences has no real concept of an index. There is no guarantee that
entries will remain in a specific order, although in reality, they will.
That's why you won;t find any "insert" style calls.
There is a nifty helper class that will save you from using sprintf. The above
lines can be written:
> for(loop = 0; loop < entries; ++loop)
> {
>if(!preference->entryExists(Fl_Preferences::Name(loop))) ...
Or for more complex labels:
> for(loop = 0; loop < entries; ++loop)
> {
>if(!preference->entryExists(Fl_Preferences::Name("menu_%d", loop))) ...
- Matthias
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Zoom on a multitouch environment
On 15.11.2011, at 17:10, Ian MacArthur wrote: > > On 15 Nov 2011, at 13:12, Mathieu Peyréga wrote: > >> The problem was solved by adding the preprocessor definition >> >> WINVER=0x0601 >> >> for both FLTK dll and the application itself... > > OK - so I guess, in that case, that the "zoom" event is being delivered to > the app as if it were a "conventional" MOUSEWHEEL event, rather than as some > new touch-specific event... > > That's interesting, and useful to know. OS X also does a similar thing: using two fingers on the touch pad will deliver MOUSEWHEEL messages to FLTK. I have not yet spent any time with any gesture APIs. Does anyone have pointers or links to good docs? ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Fl_Tile resizable() tile.cxx
On 08.12.2011, at 16:19, Robert Strickland wrote: > The behavior I would like is for each box in the tile to have some minimum > size (say 3 pixels square). Currently, when I drag the border to one side or > the other, one or more boxes completely disappears. If the user is unfamiliar > with the layout, there is absolutely no visible cue that there is a hidden > box lurking against one edge or corner of the drawn border. The poor user has > to randomly try to drag borders until the hidden box appears. Fl_Tile has no function to set a minimum tile size. However, I strongly believe that there should be one for exactly the reason you state. Using DOWN_FRAMEs for the tiles give a nice visible and draggable border, so defaulting the minimal tile size to twice the width of the border would keep the visual cue and would make it possible to reconstruct all tiles. Could you please file an STR so that we can remember to implement this? fltk.org/str.php ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Good tutorial for complex drawing functions
Thank you very much for your answers, they are good starting points for me.
What I want to do is something very simple, in the past I wrote a program to
display millions of rectangles, each is an widget, being selectable and
completely filled with an fl_rect, with a tooltip with its name and selectable
rectangle colors (a viewer for semiconductor placements).
I'm quite happy now with this simple and straightforward implementation since
on powerful machines it's fast enough. On this topic I did exchange information
with people from the forum.
Now the interesting news: there are also many components with rectilinear
shapes (like L-shape, T-shape and many more).
The easiest way - for me - would be the possibility of widgets not only x,y,w,h
but with a polygonal boundary. This would be a cool feature :-).
The second easiest way is to draw a polygon within the standard widget -
therefore were my questions below, but there is the drawback that the widget
itself is actually bigger than the physical object which creates all sorts of
problems many with select and tool tips which could show wrong object name(s).
I'm a bit stuck at the moment and thinking of the best way to implement the
polygonal objects.
Regards,
Jens
> [moved this thread from fltk.development]
> >> On 12/06/11 06:50, Jens Grunert wrote:
> >>> I want to draw comlex geometries and keep hitting this one in
> >>> the documentation: "the functionality matches that found in the Adobe
> >>> PostScript".
> >>> I searched already a lot on the net but could not find a concise, good
> >>> and easy
> >>> to read explanation of the complex drawing functions (like tranform,
> >>> scale, translate etc.).
> >>>
> >>> Does someone in the forum could point me to some good documentation
> >>> regarding
> >>> the postscript-like functionality of the complex drawing functions?
> >
> >> On Wed, Dec 7, 2011 at 2:40 AM, MacArthur, Ian (SELEX GALILEO, UK)
> >> wrote:
> >> Jens,
> >>
> >> First off, you are posting in the wrong list (the dev list is for
> >> development *of* fltk, not *using* fltk) so you will more likely get a
> >> constructive answer over in fltk.general, which is also more active
> >> anyway...
> >>
> >> > I want to draw comlex geometries and keep hitting this one in
> >> > the documentation: "the functionality matches that found in
> >> > the Adobe PostScript". [..]
> >>
> >> What are you actuallly trying to draw? If you post over in
> >> fltk.general,
> >> outlining something of what you are trying to do, I'm sure you'll get
> >> somne answers.
> >>
> >> For what it is worth, I tend to favour GL for any complex drawing
> >> anyway, so that might be your best bet, create an Fl_Gl_Window for your
> >> drawing and use regular GL drawing (for which there are many examples
> >> on
> >> the web, of course!)
>
> > On 12/07/11 05:59, E. Torres wrote:
> > Wikipedia is a good point to start with those kind of questions
> > http://en.wikipedia.org/wiki/Transformation_matrix
>
> In general I'd agree with Ian; openGL is probably the better choice
> for doing complex drawing.
>
> However, FLTK's own drawing functions (that don't involve opengl)
> do include a reasonable implementation of line drawing with scaling,
> transformation matrices, etc.
>
> For docs on the web, search for 'transformation matrix tutorial',
> or better yet, go to a bookstore and look for graphics programming books,
> such as for game programmers or 3D computer graphics. I'm sure many
> of the programmers here who work in 3D have the "Graphics Gems"
> series of books, which covers this.
>
> Also, there are surely some tutorials on PostScript that
> have a good description of the techniques.
>
> Off the top of my head regarding just scale/translate/rotate and
> matrix operations.. In general, if you've ever plotted a circle
> using sin() and cos(), you know that to get it draw on your screen,
> you can't just plot the raw sin/cos values, or you'll end up with a dot
> instead of a circle, eg:
>
> for ( float f=0; f<6.28; f+=.1 ) {
> x = sin(f);
> y = cos(f);
> plot(x,y); // results in a tiny circle
> }
>
> ..because the sin()/cos() values range from just -1 to 1.
>
> So to get the circle to show up on the screen properly, you might
> multiply the values by some constant (50), and then add some constant (80)
> so that the circle is not clipped off the screen:
>
> for ( float f=0; f<6.28; f+=.1 ) {
> x = sin(f) * 50 + 80;
> y = cos(f) * 50 + 80;
> plot(x,y); // plots a 100 pixel diameter circle
> }
>
> Here you've basically got a scale of 50 and a translation of 80.
> Just by doing that, you've learned how to scale and translate
> an object.
>
> Since all "rotation" operations fol
Re: [fltk.general] Fl_Tile resizable() tile.cxx
> > On 6 Dec 2011, at 21:48, Robert Strickland wrote: > > > I am new to FLTK. I am using fltk 1.3.0. For my application, I would = > like to establish some minimum sizes for individual tiles that make up = > the Fl_Tile. The supplied test/tile.cxx seems to have some of the = > behavior I want. Box 2a seems to have a minimum width, and box 3b seems = > to have a minimum height. This seems to be due to lines 81-82: > >=20 > > 80 > > 81 Fl_Box r(10,0,300-10,300-10); > > 82 tile.resizable(r); > > 83 // r.box(FL_BORDER_FRAME); > > 84 > >=20 > > These would appear to create an invisible box that overlaps other = > Fl_Boxes that make up the tile. If I comment out these lines, boxes 2a = > and 3b can shrink until they disappear. How does this code achieve the = > minimum sizes? > >=20 > > This seems to violate two rules for Fl_Tile: tiles shouldn't overlap = > and no more than one resizable in a tile group. > >=20 > > How can I use this same technique to make the other tiles have minimum = > sizes as well? > > What are you actually hoping to achieve, and how sure are you that = > Fl_Tile is the container you want? > > I've seen a few examples recently where people had tied themselves in = > knots doing complicated things with Fl_Tile, when it turned out that = > what they needed was just to use a few suitably nested Fl_Groups, and = > take advantage of fltk standard resize behaviours... > > So, I'm not saying that Fl_Tile is not the container you want, it may = > well be, and you know more about your application than anyone else can. = > But, you know, maybe it is the wrong thing for the job... > > Can you describe where you are trying to get to, maybe someone here will = > be able to chip in with good ideas on how to get there from here. > > In any case, as a first stab, nesting Fl_Groups inside the Fl_Tile can = > give you some control over the resize behaviour of groups of widgets = > that may alter the effects you are seeing in beneficial ways. > > > Ian, The behavior I would like is for each box in the tile to have some minimum size (say 3 pixels square). Currently, when I drag the border to one side or the other, one or more boxes completely disappears. If the user is unfamiliar with the layout, there is absolutely no visible cue that there is a hidden box lurking against one edge or corner of the drawn border. The poor user has to randomly try to drag borders until the hidden box appears. Other widget toolkits have a splitter window that will show a double bar on one edge if there is a fully minimized window lurking there. I like the idea of Fl_Tile because it can handle the entire layout with one widget instead of having a bunch of nested two-way splitters. My layout is: +--+ |Menu | +--+ |Toolbar | +--+---+ | | | |OpenGL| | +--+ | | | OpenGL | |Dialog| | | | | +--+---+ | Fl_Table | +--+ The dialog tile has buttons and editable text boxes. It needs scrollbars when its size is below a threshold. I'd like everything below the toolbar to be in an Fl_Tile. Robert ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Fl_Tile resizable() tile.cxx
> On 12/06/11 13:48, Robert Strickland wrote: > > These would appear to create an invisible box that overlaps other > > Fl_Boxes that make up the tile. > > > Yes, this is one of several techniques for controlling > which widgets will resize. > > This technique involves creating an invisible widget > that is made the 'resizable' widget for the tile; when > the tile widget is resized, the invisible widget will be > the one resized, as well as the widgets around it. > > For more info, see: > http://fltk.org/articles.php?L415+I0+THow-To+P1+Qresize Greg, I looked a the article you posted, but I don't think it addresses my questions. The box r in the tile.cxx code overlaps the visible boxes. In the resizable example, the resizable box just touches the other boxes. The line Fl_Box r(10,0,300-10,300-10); makes a box like this: 0 10300 +--+--+ 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--+ 290 | | +-+ 300 that overlaps the other boxes. This seems to form a barrier to dragging the borders between the tiles. (I commented out the lines pertaining to r. Without these lines, the borders can be dragged until they disappear.) This behavior doesn't seem to be documented in the Fl_Tile documented or commented in the tile.cxx code. I had hoped that this was part of some way to set a minimum size to boxes that form the tiles in Fl_Tile. Robert ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] I'll be back...
> Hi Matt, > > Welcome back. > If you get this far in the postings, that's you about current... Phew! Yes, I 'll have additional comments on about six threads. Special thanks to Manolo for keeping 3.0 concurrent with 1.3! ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Need FLTK C++ CODE URGENT THANKS
On 01.12.2011, at 20:13, rajesh kumar wrote: > My name is Raj. I am from CA. I a writing a C++ code compatible to FLTK tool > This is for windows > Basically my requrement is I have a Water Tank. > When i click on the water tank the fish image should appear and we should > move the fish in the water tank by dragging the mouse. > > I need a C++ code for this one. If you need any thing let me know. > > Thanks a lott for your help and i am so grate full to you > Thanks, > RAJ Sorry, we don't do homework. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Fl_File_Chooser(common dialog) and Favorites Menu_button
On 10.10.2011, at 23:46, david mcclanahan wrote: > I want to preseed the list of directories under "Favorites" with a directory > containing some sample files that gets determined at install time. I don't > see any obvious way to allow to do it and wanted to make sure that was the > case. There is an underlying Fl_Prefs object but it's private(FLTK ver > 1.3.0). I may see if I can modify the underlying file if I can determine > where it is in a stable manner. > > > Anyway is this purposely done? Someone went to a lot of trouble to allow one > to relabel buttons and such so I find it hard to believe you can't > programmatically change items in that menu. You can change items in the menu, but it is not a good practice. This menu is meant for the user, because it is used in all FLTK apps, not just in your own app. You can access the file using Fl_Preferences(Fl_Preferences::USER, "fltk.org", "filechooser"); ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Fl_Overlay_Windows.cxx : strange 'g' char
> in Fl_Overlay_Windows.cxx, there is a strange include > directive line 25 : > > #include g > > (branch 1.3 - r9200) OK - try 9201 SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
[fltk.general] Fl_Overlay_Windows.cxx : strange 'g' char
Hi, in Fl_Overlay_Windows.cxx, there is a strange include directive line 25 : #include g (branch 1.3 - r9200) Regards, David ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] I'll be back...
> Sorry folks for my sudden absence without first applying for > an unpaid leave ;-) . This thing that I do occasionally > called "my job" demanded my full attention. > > Now that I am 500+ postings behind, I will use the next days > to catch up and find out what was going on. After that, I > will hopefully have enough time to continue on FLTK 3.0. > > Again, sorry for not having checked in for such a long time. Hi Matt, Welcome back. If you get this far in the postings, that's you about current... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
