The 2 public methods should be called each time the triangulation is changing.
2 other methods have been added :lock and unlock. when locked this node does not draw anything in glrender
+
removed lines too long
The 2 public methods should be called each time the triangulation is changing.
2 other methods have been added :lock and unlock. when locked this node does not draw anything in glrender
+
removed lines too long
The 2 public methods should be called each time the triangulation is changing.
2 other methods have been added :lock and unlock. when locked this node does not draw anything in glrender
+
removed lines too long
The 2 public methods should be called each time the triangulation is changing.
2 other methods have been added :lock and unlock. when locked this node does not draw anything in glrender
border, one can use a QFrame parent of the Qt_widget. It will be probably
more efficient. Thank to Radu for not having agreed to easily: it
prevended my from doing an error. ;-)
functions set ranges (xmin,ymin,xmax,ymax) with constant center. Arguments
where always equal to xcenter, ycenter thus they were uneeded.
- Use drawContents(QPainter*), the protected method of QFrame called by
QFrame::paintEvent(...). paintEvent(...) is no longer overridden.
- Added comments in include/CGAL/IO/Qt_widget.h to explain the role of
private functions. It was increasingly difficult to understand the code.
- New void Qt_widget::frameChanged() function, that resize the pixmap if
the frame border is changed.
- It now derives from QToolBar, as it should have since the beginning.
- The constructor has now additional facultative parameters:
Dock = DockTop,
bool newLine = true,
const char* name = 0
With Qt-3, the first parameter is
QMainWindow::ToolBarDock=QMainWindow::Top
- The header file has been cleaned from uneeded includes or pointer
declarations.
- The backward compatibility has been preserved by adapted default values.
- I have filled bug #36 for as a reminder for documentation changes.
but is quite small actually:
Qt_widget now derives from QFrame instead of QWidget. The differences are
that:
- the Qt_widget can have a border, like a QFrame
- the drawing area is not the whole Qt_widget but the contentsRect()
rectangle, which is the widget without its border.
As, by default, the border is null, it should change anything for
compatibility. By default, a QFrame is like a QWidget.