- Jul 07, 2010
-
-
hjk authored
-
- Jul 06, 2010
- Jul 05, 2010
-
-
hjk authored
-
- Jul 02, 2010
-
-
hjk authored
... by stripping out 'const', 'volatile', 'struct' and 'class'.
-
- Jul 01, 2010
- Jun 30, 2010
-
-
hjk authored
-
- Jun 29, 2010
- Jun 28, 2010
- Jun 25, 2010
- Jun 23, 2010
-
-
hjk authored
This is handled by the generic pointer case nowadays and was (now) wrong as it was impossible to see the 'bald pointer' version of it.
-
- Jun 22, 2010
-
-
hjk authored
This replaces the (de facto) singleton engines and data handlers by classes that are instantiated per run. The DebuggerRunControl will now create an object of (a class derived from) DebuggerEngine that contains all the relevant "dynamic" data. DebuggerManager is no more. The "singleton" bits are merged into DebuggerPlugin, whereas the data bits went to DebuggerEngine. There is no formal notion of a "current" DebuggerEngine. However, as there's only one DebuggerEngine at a time that has its data models connected to the view, there's still some "de facto" notion of a "current" engine. Calling SomeModel::setData(int role, QVariant data) with custom role is used as the primary dispatch mechanism from the views to the "current" data models (and the engine, as all data models know their engine).
-
- Jun 14, 2010
-
-
hjk authored
-
- Jun 11, 2010
-
-
hjk authored
refactoring
-
- Jun 10, 2010
- Jun 08, 2010
- Jun 01, 2010
-
-
hjk authored
-
- May 28, 2010
-
-
hjk authored
-
- May 27, 2010
-
-
hjk authored
Reviewed-By: Oswald Buddenhagen
-
- May 26, 2010
-
-
hjk authored
The value was adjusted to the referenced value but it was not used when dumping the members, basically leading to an empty child list in such cases.
- May 20, 2010