The documentation can also be accessed online. The docs on the web site are usually somewhat older latest release. Generation of Documentation common part : To generate the documentation yourself, you should have Doxygen version 1. Older Doxygen versions than 1. You can use the packages tetex older or texlive current if your distribution provides them.

Author:Samuzragore Gardagal
Language:English (Spanish)
Published (Last):1 July 2009
PDF File Size:1.36 Mb
ePub File Size:1.62 Mb
Price:Free* [*Free Regsitration Required]

This is different than an idle callback because it is only called once, then FLTK calls the system and tells it not to return until an event happens. The advantage of using a check callback is that it is called only when no events are pending.

If events are coming in quickly, whole blocks of them will be processed before this is called once. This can save significant time and avoid the application falling behind the events. When the fd becomes ready for reading Fl::wait will call the callback and then return. There can only be one callback of each type for a file descriptor.

Under UNIX any file descriptor can be monitored files, devices, pipes, sockets, etc. If FLTK cannot figure out what to do with an event, it calls each of these functions most recent first until one of them returns non-zero. If none of them returns non zero then the event is ignored. This lets you provide global shortcut keys. System events that FLTK does not recognize.

Some other events when the widget FLTK selected returns zero from its handle method. Exactly which ones may change in future versions, however. The idle function can be used to get background processing done. You can have multiple idle callbacks. Fl::wait and Fl::check call idle callbacks, but Fl::ready does not. FLTK will not recursively call the idle callback.

Add a one-shot timeout callback. The function will be called by Fl::wait at t seconds after this function is called. You can have multiple timeout callbacks. Returns the number of words eaten 1 or 2, or 0 if it is not recognized and adds the same value to i.

You can use this function if you prefer to control the incrementing through the arguments yourself. Everything it can do can be done with other calls to FLTK. To use the switch parser, call Fl::args This does not open the display, instead switches that need the display open are stashed into static variables. It is called with the same argc and argv, and with i the index of each word.

The callback should return zero if the switch is unrecognized, and not change i. It should return non-zero if the switch is recognized, and add at least 1 to i it can add more to consume words after the switch. This function is called before any other tests, so you can override any FLTK switch this is why FLTK can use very short switches instead of the long ones all other toolkits force you to use.

On return i is set to the index of the first non-switch. If your program takes no arguments other than switches you should produce an error if the return value is less than argc. All switches except -bg2 may be abbreviated one letter and case is ignored: -bg color or -background color Sets the background color using Fl::background.

The second form of Fl::args is useful if your program does not have command line switches of its own. It parses all the switches, and if any are not recognized it calls Fl::abort Fl::help. A usage string is displayed if Fl::args detects an invalid argument on the command-line.

You can change the message by setting the Fl::help pointer.










Related Articles