• 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).