diff options
author | Johannes Hofmann <Johannes.Hofmann@gmx.de> | 2010-08-20 23:24:19 +0200 |
---|---|---|
committer | Johannes Hofmann <Johannes.Hofmann@gmx.de> | 2010-08-20 23:24:19 +0200 |
commit | f5c598b518d1f906148534d015f50075d3e8242d (patch) | |
tree | 21dd70add5b366c3dd80641b77f6b18e0baa009e /doc/fltk-problems.doc | |
parent | e98d02a01ffeb18ede86af025e51ae1ec011c75a (diff) | |
parent | 5f0fc0e48b8cbee7e1795935da0abff6627fd498 (diff) |
merge
Diffstat (limited to 'doc/fltk-problems.doc')
-rw-r--r-- | doc/fltk-problems.doc | 37 |
1 files changed, 7 insertions, 30 deletions
diff --git a/doc/fltk-problems.doc b/doc/fltk-problems.doc index 3e8c401f..6f20c44d 100644 --- a/doc/fltk-problems.doc +++ b/doc/fltk-problems.doc @@ -5,19 +5,6 @@ Current problems: <ul> -<li> dw::fltk::FltkViewport::draw should only draw the region, for which e.g. - an expose event was received. - -<li> dw::fltk::FltkViewport::queueDraw will collect data, which has to be - redrawn. Currently, it calls redraw (DAMAGE_EXPOSE), can this be changed, - so that dw::fltk::FltkViewport::draw will distinguish between the two - cases? - -<li> For Scrolling, something similar applies, only parts of the viewport - have to be redrawn. - -<li> Also for Scrolling, it is necessary to copy parts of the window. - <li> How should dw::fltk::FltkViewport::cancelQueueDraw be implemented? <li> If the value of a scrollbar is changed by the program, not the user, @@ -27,12 +14,7 @@ Current problems: <li> Also, the problems with the widgets seems to work. Also sure? -<li> When drawing, clipping of 32 bit values seems to work. - -<li> Who is responsable for clearing before drawing? - -<li> The embedded buttons are not redrawn, when pressing the mouse button - on them. +<li> When drawing, clipping of 32 bit values is not working properly. <li> The item group within a selection widget (menu) should not be selectable. </ul> @@ -74,11 +56,6 @@ perhaps different implementations for different window systems could be used. Then, it is for X necessary to use GCs with clipping masks. -<h2>Lower Priority</h2> - -There needs to be an XEmbed implementation. - - <h2>dw::fltk::ui::ComplexButton</h2> Unfortunately, FLTK does not provide a button with Group as parent, so @@ -106,7 +83,7 @@ The following changes should be applied manually. <h3>Changes in fltkcomplexbutton.hh</h3> -First of all, the #define's for avoiding multiple includes: +First of all, the \#define's for avoiding multiple includes: \code -#ifndef fltk_ComplexButton_h // fltk_Button_h formerly @@ -133,7 +110,7 @@ at the end. Then, the namespace is changed: at the beginning and -\code +\code -} +} // namespace ui +} // namespace fltk @@ -151,7 +128,7 @@ at the end. Most important, the base class is changed: and -\code +\code -class FL_API ComplexButton : public Widget { +class ComplexButton: public ::fltk::Group +{ @@ -167,10 +144,10 @@ namespace conflict: <h3>Changes in fltkcomplexbutton.cc</h3> -First, #include's: +First, \#include's: \code - + #include <fltk/events.h> #include <fltk/damage.h> -#include <fltk/ComplexButton.h> // <fltk/Button.h> formerly @@ -216,4 +193,4 @@ dw::fltk::ui::ComplexButton::draw()): } \endcode -*/
\ No newline at end of file +*/ |