Next: FL (uppercase) Prev: AL (uppercase) Up: SGI IRIX ONLY Top: Top
fl
markov@cs.ruu.nl
.
Most functions are literal translations of their C equivalents,
dropping the initial `fl_' from their name. Constants used by the
library are defined in module FL
described below.
The creation of objects is a little different in Python than in C:
instead of the `current form' maintained by the library to which new
FORMS objects are added, all functions that add a FORMS object to a
button are methods of the Python object representing the form.
Consequently, there are no Python equivalents for the C functions
fl_addto_form
and fl_end_form
, and the equivalent of
fl_bgn_form
is called fl.make_form
.
Watch out for the somewhat confusing terminology: FORMS uses the word object for the buttons, sliders etc. that you can place in a form. In Python, `object' means any value. The Python interface to FORMS introduces two new Python object types: form objects (representing an entire form) and FORMS objects (representing one button, slider etc.). Hopefully this isn't too confusing...
There are no `free objects' in the Python interface to FORMS, nor is there an easy way to add object classes written in Python. The FORMS interface to GL event handling is avaiable, though, so you can mix FORMS with pure GL windows.
Please note: importing fl
implies a call to the GL function
foreground()
and to the FORMS routine fl_init()
.