1. 22 Jun, 2010 6 commits
    • hjk's avatar
      debugger: work on action handling · 817dbabd
      hjk authored
      817dbabd
    • hjk's avatar
      debugger: more breakpoint management related fixes · fadac800
      hjk authored
      fadac800
    • hjk's avatar
      c5c0dc76
    • Friedemann Kleint's avatar
      Compile Windows. · ecff29be
      Friedemann Kleint authored
      ecff29be
    • hjk's avatar
      debugger: connect some loose ends · f1cd284a
      hjk authored
      f1cd284a
    • hjk's avatar
      debugger: The DebuggerEngine refactoring. · 6a6cba55
      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).
      6a6cba55