- Aug 26, 2010
-
-
Christian Kandeler authored
This will help us diagnose errors.
-
- Aug 20, 2010
-
-
Friedemann Kleint authored
Fix breakage introduced by the new asynchronous stop() methods of the debugger run controls. Allow for RunControl::stop() to be asynchronous by introducing a return enumeration indicating that. Introduce additional method aboutToStop() asking user to quit (tie that to the RunControl instead of having to hack the behaviour elsewhere). If asynchronous stop is detected, terminate the ProjectExplorer asynchronously. This makes the behaviour consistent across switching sessions/ closing outputwindow tabs and quitting Qt Creator. Reviewed-by: dt Rubber-stamped-by: hjk
-
- Aug 10, 2010
- Jul 15, 2010
-
-
ck authored
Use Debugger::DebuggerRunControl directly instead of wrapping it into another RunControl. Reviewed-by: hjk
-
- Jul 14, 2010
-
-
ck authored
Preparation for removing MaemoDebugRunControl. Reviewed-by: kh1
-
- Jul 13, 2010
-
-
ck authored
Reviewed-by: kh1
-
- Jul 12, 2010
-
-
ck authored
-
- Jul 08, 2010
-
-
ck authored
Reviewed-by: kh1
-
- Jul 06, 2010
-
-
ck authored
No difference in functionality yet. Reviewed-by: kh1
-
- Jun 24, 2010
-
-
ck authored
-
- Jun 23, 2010
- Jun 22, 2010
-
-
ck authored
Task-number: QTCREATORBUG-1636 Reviewed-by: kh1
-
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 21, 2010
-
-
ck authored
Reviewed-by: kh1
-
- May 05, 2010
-
-
ck authored
Reviewed-by: hjk
-
- May 03, 2010
-
-
dt authored
And use it to implement changing the run icon in the application output. That implementation does only support the two run modes run and debug for now. Further abstraction for more run modes to be done once needed. Task-Nr: QTCREATORBUG-1232
-
- Apr 20, 2010
-
-
ck authored
-
- Apr 19, 2010
-
-
Erik Verbruggen authored
So now the "Applciation Output" can distinguish between these four, and handle them appropriately.
-
ck authored
Reviewed-by: kh1
-
ck authored
Reviewed-by: kh1
-
- Apr 15, 2010
-
-
ck authored
Reviewed-by: kh1
-
- Apr 13, 2010
- Apr 12, 2010
-
-
ck authored
Reviewed-by: kh1
-
- Apr 07, 2010
-
-
ck authored
-
- Mar 18, 2010
-
-
Friedemann Kleint authored
-
- Mar 09, 2010
-
-
ck authored
-
- Mar 05, 2010
- Feb 08, 2010
-
-
ck authored
-
- Feb 03, 2010
-
-
ck authored
Reviewed-by: kh1
-
- Jan 11, 2010
-
-
ck authored
-
- Jan 06, 2010
-
-
ck authored
The maemorunconfiguration.cpp file contained (and still contains) too many different classes.
-