| Version: 3.0.5

- Main Page
- Related Pages
- Categories
- Classes
- Files

All Classes Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Modules Pages
Reference Counting

Many wxWidgets objects use a technique known as reference counting, also known as copy on write (COW).

This means that when an object is assigned to another, no copying really takes place. Only the reference count on the shared object data is incremented and both objects share the same data (a very fast operation).

But as soon as one of the two (or more) objects is modified, the data has to be copied because the changes to one of the objects shouldn't be seen in the others. As data copying only happens when the object is written to, this is known as COW.

What is important to understand is that all this happens absolutely transparently to the class users and that whether an object is shared or not is not seen from the outside of the class - in any case, the result of any operation on it is the same.

# Object Comparison

The == and != operators of the reference counted classes always do a deep comparison. This means that the equality operator will return true if two objects are identical and not only if they share the same data.

Note that wxWidgets follows the STL philosophy: when a comparison operator cannot be implemented efficiently (like for e.g. wxImage's == operator which would need to compare the entire image's data, pixel-by-pixel), it's not implemented at all. That's why not all reference counted classes provide comparison operators.

Also note that if you only need to do a `shallow` comparison between two wxObject derived classes, you should not use the == and != operators but rather the wxObject::IsSameAs() function.

# Object Destruction

When a COW object destructor is called, it may not delete the data: if it's shared, the destructor will just decrement the shared data's reference count without destroying it. Only when the destructor of the last object owning the data is called, the data is really destroyed. Just like all other COW-things, this happens transparently to the class users so that you shouldn't care about it.

# List of Reference Counted Classes

The following classes in wxWidgets have efficient (i.e. fast) assignment operators and copy constructors since they are reference-counted:

- wxAcceleratorTable
- wxAnimation
- wxBitmap
- wxBrush
- wxCursor
- wxFont
- wxGraphicsBrush
- wxGraphicsContext
- wxGraphicsFont
- wxGraphicsMatrix
- wxGraphicsPath
- wxGraphicsPen
- wxIcon
- wxImage
- wxMetafile
- wxPalette
- wxPen
- wxRegion
- wxVariant
- wxVariantData

Note that the list above reports the objects which are reference counted in all ports of wxWidgets; some ports may use this technique also for other classes.

All the objects implement a function IsOk() to test if they are referencing valid data; when the objects are in uninitialized state, you can only use the IsOk() getter; trying to call any other getter, e.g. wxBrush::GetStyle() on the wxNullBrush object, will result in an assert failure in debug builds.

# Making Your Own Reference Counted Class

Reference counting can be implemented easily using wxObject or using the intermediate wxRefCounter class directly. Alternatively, you can also use the wxObjectDataPtr<T> template.

First, derive a new class from wxRefCounter (or wxObjectRefData when using a wxObject derived class) and put the memory-consuming data in it.

Then derive a new class from wxObject and implement there the public interface which will be seen by the user of your class. You'll probably want to add a function to your class which does the cast from wxObjectRefData to your class-specific shared data. For example:

MyClassRefData* GetData() const
{
return wx_static_cast(MyClassRefData*, m_refData);
}

In fact, any time you need to read the data from your wxObject-derived class, you will need to call this function.

Note
  Any time you need to actually modify the data placed inside your wxObject derived class, you must first call the wxObject::UnShare() function to ensure that the modifications won't affect other instances which are eventually sharing your object's data.