]>
Commit | Line | Data |
---|---|---|
3980000c | 1 | \section{Runtime class information (aka RTTI) overview}\label{runtimeclassoverview} |
a660d684 KB |
2 | |
3 | Classes: \helpref{wxObject}{wxobject}, \helpref{wxClassInfo}{wxclassinfo}. | |
4 | ||
34636400 | 5 | One of the failings of C++ used to be that no run-time information was provided |
a660d684 | 6 | about a class and its position in the inheritance hierarchy. |
34636400 VZ |
7 | Another, which still persists, is that instances of a class cannot be created |
8 | just by knowing the name of a class, which makes facilities such as persistent | |
9 | storage hard to implement. | |
a660d684 KB |
10 | |
11 | Most C++ GUI frameworks overcome these limitations by means of a set of | |
fc2171bd | 12 | macros and functions and wxWidgets is no exception. As it originated before the |
3980000c | 13 | addition of RTTI to the C++ standard and as support for it is still missing from |
fc2171bd | 14 | some (albeit old) compilers, wxWidgets doesn't (yet) use it, but provides its |
34636400 VZ |
15 | own macro-based RTTI system. |
16 | ||
17 | In the future, the standard C++ RTTI will be used though and you're encouraged | |
f70c0443 | 18 | to use whenever possible the \helpref{wxDynamicCast()}{wxdynamiccast} macro which, |
34636400 | 19 | for the implementations that support it, is defined just as dynamic\_cast<> and |
fc2171bd | 20 | uses wxWidgets RTTI for all the others. This macro is limited to wxWidgets |
34636400 | 21 | classes only and only works with pointers (unlike the real dynamic\_cast<> which |
f6bcfd97 | 22 | also accepts references). |
34636400 | 23 | |
f70c0443 | 24 | Each class that you wish to be known to the type system should have |
a660d684 KB |
25 | a macro such as DECLARE\_DYNAMIC\_CLASS just inside the class declaration. |
26 | The macro IMPLEMENT\_DYNAMIC\_CLASS should be in the implementation file. | |
6b037754 JS |
27 | Note that these are entirely optional; use them if you wish to check object |
28 | types, or create instances of classes using the class name. However, | |
29 | it is good to get into the habit of adding these macros for all classes. | |
a660d684 | 30 | |
f4fcc291 | 31 | Variations on these \helpref{macros}{rttimacros} are used for multiple inheritance, and abstract |
a660d684 KB |
32 | classes that cannot be instantiated dynamically or otherwise. |
33 | ||
34 | DECLARE\_DYNAMIC\_CLASS inserts a static wxClassInfo declaration into the | |
35 | class, initialized by IMPLEMENT\_DYNAMIC\_CLASS. When initialized, the | |
36 | wxClassInfo object inserts itself into a linked list (accessed through | |
37 | wxClassInfo::first and wxClassInfo::next pointers). The linked list | |
38 | is fully created by the time all global initialisation is done. | |
39 | ||
40 | IMPLEMENT\_DYNAMIC\_CLASS is a macro that not only initialises the static | |
41 | wxClassInfo member, but defines a global function capable of creating a | |
42 | dynamic object of the class in question. A pointer to this function is | |
43 | stored in wxClassInfo, and is used when an object should be created | |
44 | dynamically. | |
45 | ||
34636400 VZ |
46 | \helpref{wxObject::IsKindOf}{wxobjectiskindof} uses the linked list of |
47 | wxClassInfo. It takes a wxClassInfo argument, so use CLASSINFO(className) | |
48 | to return an appropriate wxClassInfo pointer to use in this function. | |
a660d684 KB |
49 | |
50 | The function \helpref{wxCreateDynamicObject}{wxcreatedynamicobject} can be used | |
51 | to construct a new object of a given type, by supplying a string name. | |
52 | If you have a pointer to the wxClassInfo object instead, then you | |
f70c0443 | 53 | can simply call \helpref{wxClassInfo::CreateObject}{wxclassinfocreateobject}. |
a660d684 KB |
54 | |
55 | \subsection{wxClassInfo}\label{wxclassinfooverview} | |
56 | ||
3980000c | 57 | \overview{Runtime class information (aka RTTI) overview}{runtimeclassoverview} |
a660d684 KB |
58 | |
59 | Class: \helpref{wxClassInfo}{wxclassinfo} | |
60 | ||
61 | This class stores meta-information about classes. An application | |
62 | may use macros such as DECLARE\_DYNAMIC\_CLASS and IMPLEMENT\_DYNAMIC\_CLASS | |
63 | to record run-time information about a class, including: | |
64 | ||
65 | \begin{itemize}\itemsep=0pt | |
66 | \item its position in the inheritance hierarchy; | |
67 | \item the base class name(s) (up to two base classes are permitted); | |
68 | \item a string representation of the class name; | |
69 | \item a function that can be called to construct an instance of this class. | |
70 | \end{itemize} | |
71 | ||
72 | The DECLARE\_... macros declare a static wxClassInfo variable in a class, which is initialized | |
73 | by macros of the form IMPLEMENT\_... in the implementation C++ file. Classes whose instances may be | |
74 | constructed dynamically are given a global constructor function which returns a new object. | |
75 | ||
76 | You can get the wxClassInfo for a class by using the CLASSINFO macro, e.g. CLASSINFO(wxFrame). | |
77 | You can get the wxClassInfo for an object using wxObject::GetClassInfo. | |
78 | ||
79 | See also \helpref{wxObject}{wxobject} and \helpref{wxCreateDynamicObject}{wxcreatedynamicobject}. | |
80 | ||
a203f6c0 | 81 | \subsection{Example}\label{runtimeclassinformationexample} |
a660d684 | 82 | |
34636400 | 83 | In a header file frame.h: |
a660d684 KB |
84 | |
85 | \begin{verbatim} | |
34636400 | 86 | class wxFrame : public wxWindow |
a660d684 | 87 | { |
34636400 VZ |
88 | DECLARE_DYNAMIC_CLASS(wxFrame) |
89 | ||
90 | private: | |
91 | wxString m_title; | |
a660d684 | 92 | |
34636400 VZ |
93 | public: |
94 | ... | |
a660d684 KB |
95 | }; |
96 | \end{verbatim} | |
97 | ||
34636400 | 98 | In a C++ file frame.cpp: |
a660d684 KB |
99 | |
100 | \begin{verbatim} | |
101 | IMPLEMENT_DYNAMIC_CLASS(wxFrame, wxWindow) | |
102 | ||
34636400 | 103 | wxFrame::wxFrame() |
a660d684 KB |
104 | { |
105 | ... | |
106 | } | |
107 | \end{verbatim} | |
108 | ||
109 |