Inherited by GlutWindow.
Public Member Functions | |
void | create () |
void | flush () |
void | destroy () |
void | layout () |
char | valid () const |
void | valid (char i) |
void | invalidate () |
int | mode () const |
bool | mode (int a) |
bool | can_do () const |
GLContext | context () const |
void | context (GLContext v, bool destroy_flag=false) |
void | make_current () |
void | swap_buffers () |
void | ortho () |
bool | can_do_overlay () |
void | redraw_overlay () |
void | hide_overlay () |
void | make_overlay_current () |
~GlWindow () | |
GlWindow (int W, int H, const char *l=0) | |
GlWindow (int X, int Y, int W, int H, const char *l=0) | |
virtual void | draw ()=0 |
virtual void | draw_overlay () |
Static Public Member Functions | |
bool | can_do (int) |
Friends | |
class | GlOverlay |
draw() is a pure virtual method. You must subclass GlWindow and provide an implementation for draw(). You can avoid reinitializing the viewport and lights and other things by checking valid() at the start of draw() and only doing the initialization if it is false.
draw() can only use OpenGL calls. Do not attempt to call any of the functions in <fltk/draw.h>, or X or GDI32 or any other drawing api. Do not call glstart() or glfinish().
Normally double-buffering is enabled. You can disable it by chaning the mode() to turn off the DOUBLE_BUFFER bit.
If double-buffering is enabled, the back buffer is made current before draw() is called, and the back and front buffers are automatically swapped after draw() is completed.
Some tricks using the front buffer require you to control the swapping. You can call swap_buffers() to swap them (OpenGL does not provide a portable function for this, so we provide it). But you will need to turn off the auto-swap, you do this by adding the NO_AUTO_SWAP bit to the mode().
The method draw_overlay() is a second drawing operation that is put atop the main image. You can implement this, and call redraw_overlay() to indicate that the image in this overlay has changed and that draw_overlay() must be called.
Originally this was written to support hardware overlays, but FLTK emulated it if the hardware was missing so programs were portable. FLTK 2.0 is not normally compiled to support hardware overlays, but the emulation still remains, so you can use these functions. (Modern hardware typically has no overlays, and besides it is fast enough that the original purpose of them is moot)
By default the emulation is to call draw_overlay() after draw() and before swapping the buffers, so the overlay is just part of the normal image and does not blink. You can get some of the advantages of overlay hardware by setting the GL_SWAP_TYPE environment variable, which will cause the front buffer to be used for the draw_overlay() method, and not call draw() each time the overlay changes. This will be faster if draw() is very complex, but the overlay will blink. GL_SWAP_TYPE can be set to:
|
The destructor will destroy the context() if it belongs to the window. |
|
The constructor sets the mode() to RGB_COLOR|DEPTH_BUFFER|DOUBLE_BUFFER which is probably all that is needed for most 3D OpenGL graphics. |
|
Returns true if the hardware supports the current value of mode(). If false, attempts to show or draw this window will cause an error(). |
|
Returns true if the hardware supports mode, see mode() for the meaning of the bits. |
|
Return true if the hardware supports OpenGL overlay planes, and FLTK has been compiled to use them. If true, draw_overlay() will be called with OpenGL setup to draw these overlay planes, and redraw_overlay() will not cause the main draw() to be called. |
|
Set the OpenGL context object to use to draw this window. This is a system-dependent structure (HGLRC on Windows,GLXContext on X, and AGLContext (may change) on OS/X), but it is portable to copy the context from one window to another. You can also set it to NULL, which will force FLTK to recreate the context the next time make_current() is called, this is useful for getting around bugs in OpenGL implementations. destroy_flag indicates that the context belongs to this window and should be destroyed by it when no longer needed. It will be destroyed when the window is destroyed, or when the mode() is changed, or if the context is changed to a new value with this call. |
|
Return the current OpenGL context object being used by this window, or 0 if there is none. |
|
Besides getting rid of the window, this will destroy the context if it belongs to the window. Reimplemented from Window. |
|
You must implement this virtual function if you want to draw into the overlay. The overlay is cleared before this is called (unless the NO_ERASE_OVERLAY bit is set in the mode and hardware overlay is supported). You should draw anything that is not clear using OpenGL. If the hardware overlay is being used it will probably be color indexed. You must use glsetcolor() to choose colors (it allocates them from the colormap using system-specific calls), and remember that you are in an indexed OpenGL mode and drawing anything other than flat-shaded will probably not work. Depending on the OS and whether or not the overlay is being simulated, the context may be shared with the main window. This means if you check valid() in draw() to avoid initialization, you must do so here and initialize to exactly the same setting. Reimplemented from Window. |
|
Turn off valid(). |
|
Selects the OpenGL context for the widget, creating it if necessary. It is called automatically prior to the draw() method being called. You can call it in handle() to set things up to do OpenGL hit detection, or call it other times to do incremental update of the window. Reimplemented in GlutWindow. |
|
Selects the OpenGL context for the widget's overlay. This can be used to do incremental OpenGL drawing into the overlay. If hardware overlay is not supported, this sets things to draw into the front buffer, which is probably not good enough emulation to be usable. |
|
Set or change the OpenGL capabilites of the window. The value can be any of the symbols from <fltk/visual.h> OR'd together:
If the desired combination cannot be done, FLTK will try turning off MULTISAMPLE and STERERO. If this also fails then attempts to create the context will cause error() to be called, aborting the program. Use can_do() to check for this and try other combinations. You can change the mode while the window is displayed. This is most useful for turning double-buffering on and off. Under X this will cause the old X window to be destroyed and a new one to be created. If this is a top-level window this will unfortunately also cause the window to blink, raise to the top, and be de-iconized, and the ID will change, possibly breaking other code. It is best to make the GL window a child of another window if you wish to do this! |
|
Set the projection so 0,0 is in the lower left of the window and each pixel is 1 unit wide/tall. If you are drawing 2D images, your draw() method may want to call this when valid() is false. |
|
Causes draw_overlay() to be called at a later time. Initially the overlay is clear, if you want the window to display something in the overlay when it first appears, you must call this immediately after you show() your window. Reimplemented from Window. |
|
Swap the front and back buffers of this window (or copy the back buffer to the front, possibly clearing or garbaging the back one, depending on your OpenGL implementation. This is called automatically after draw() unless the NO_AUTO_SWAP flag is set in the mode(). |
|
This flag is turned off on a new window or if the window is ever resized or the context is changed. It is turned on after draw() is called. draw() can use this to skip initializing the viewport, lights, or other pieces of the context.
void My_GlWindow_Subclass::draw() { if (!valid()) { glViewport(0,0,w(),h()); glFrustum(...); glLight(...); glEnable(...); ...other initialization... } ... draw your geometry here ... } |