summaryrefslogtreecommitdiffstats
path: root/src/gui/general/CanvasItemGC.h
diff options
context:
space:
mode:
Diffstat (limited to 'src/gui/general/CanvasItemGC.h')
-rw-r--r--src/gui/general/CanvasItemGC.h10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/gui/general/CanvasItemGC.h b/src/gui/general/CanvasItemGC.h
index db1833b..681e021 100644
--- a/src/gui/general/CanvasItemGC.h
+++ b/src/gui/general/CanvasItemGC.h
@@ -29,7 +29,7 @@
#include <vector>
-class QCanvasItem;
+class TQCanvasItem;
namespace Rosegarden
@@ -47,12 +47,12 @@ namespace Rosegarden
* The problem this solves is a classic ownership/double deletion
* case. The SegmentCanvas deletes all its items on destruction. But
* the SegmentItems have an auxiliary "repeat rectangle" which is a
- * QCanvasRectangle, that needs to be deleted when the SegmentItem is
+ * TQCanvasRectangle, that needs to be deleted when the SegmentItem is
* itself deleted.
*
* However, if the SegmentItem deletes its repeat rectangle, then when
* the SegmentCanvas destruction occurs, the SegmentCanvas dtor will
- * get a list of all its children (QCanvas::allItems()), containing
+ * get a list of all its children (TQCanvas::allItems()), containing
* both SegmentItems and their repeat rectangles. Deleting a
* SegmentItem will delete its repeat rectangle, which will still be
* present in the all children list which the SegmentCanvas dtor is
@@ -66,7 +66,7 @@ class CanvasItemGC
{
public:
/// mark the given item for GC
- static void mark(QCanvasItem*);
+ static void mark(TQCanvasItem*);
/// GC all marked items
static void gc();
@@ -75,7 +75,7 @@ public:
static void flush();
protected:
- static std::vector<QCanvasItem*> m_garbage;
+ static std::vector<TQCanvasItem*> m_garbage;
};