- Nov 18, 2010
- Nov 16, 2010
-
-
hjk authored
-
hjk authored
-
hjk authored
To keep the breakpoint state machinery simple
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
-
Friedemann Kleint authored
Remove BreakHandler::hasPendingBreakpoints, handle new types in CDB and gdb. Start fixing Breakpoint-Dialog. Add assignment of Breakpointresponse from BreakpointParameters. Reviewed-by: hjk
-
- Nov 15, 2010
-
-
hjk authored
-
hjk authored
-
Friedemann Kleint authored
For Breakpoint data manipulation. Reviewed-by: hjk
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
-
Friedemann Kleint authored
-
hjk authored
-
hjk authored
-
hjk authored
FIXME: add translations once interface has stabilized.
-
hjk authored
It also shows the response data.
-
hjk authored
-
hjk authored
-
hjk authored
-
hjk authored
The breakpoints are now (fairly) tightly guarded by the BreakpointHandler. Engines and Views are only supposed to refer to them by id. They also have individual states now. The breakpoint data is split into a "user requested" "fixed" part in BreakpointData and the engines' acknowledged data in a new struct BreakpointResponse. TODO: Move m_state and m_engine members to BreakpointResponse. Fix regressions in the marker handling.
-
- Nov 10, 2010
- Nov 05, 2010
-
-
hjk authored
-
- Nov 04, 2010
-
-
hjk authored
-
- Nov 02, 2010
-
-
Friedemann Kleint authored
-
- Oct 29, 2010
-
-
hjk authored
-