summaryrefslogtreecommitdiff
path: root/src/plugins/debugger/debuggeruiswitcher.cpp
Commit message (Collapse)AuthorAgeFilesLines
* debugger: move DebuggerMainWindow to debuggermainwindow.{h,cpp}hjk2010-12-021-700/+0
|
* debugger: merger DebuggerMainWindow and DebuggerUISwitcherhjk2010-12-021-84/+100
|
* debugger: DebuggerUISwitcher code reorghjk2010-12-021-67/+60
|
* debugger: make DebuggerMode derive directly from IMode instead of BaseModehjk2010-12-021-21/+19
|
* debugger: Refactor breakpoint handling.hjk2010-11-151-29/+27
| | | | | | | | | | | 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.
* debugger: refactoring of the plugin interfacehjk2010-11-101-29/+4
| | | | | There's some 'external' and some 'internal' part now. Other plugins are only supposed the external interface.
* debugger: move logical ownership of breakhandler from engines to pluginhjk2010-11-041-2/+2
|
* Coreplugin: Header cleanup.Friedemann Kleint2010-11-021-0/+1
| | | | Clean icore.h.
* ProjectExplor/Debugger: Header cleanupFriedemann Kleint2010-11-021-7/+0
|
* Debugger: Remove explicit language switch from menuKai Koehne2010-09-281-78/+17
| | | | | | This duplicates the switch in the runtime configuration. Reviewed-by: Lasse Holmstedt
* QmlDebugger: Fix qDebug outputKai Koehne2010-09-221-2/+2
|
* Compile warnings in DebuggerUISwitcherFriedemann Kleint2010-09-131-9/+24
|
* coreplugin: use Core::Id is some placeshjk2010-09-101-9/+9
|
* debugger: show "Memory..." menu entry only in debug modehjk2010-09-101-1/+2
|
* debugger: code cosmeticshjk2010-09-101-65/+66
|
* debugger: add an "Memory View" item to the menuhjk2010-09-091-16/+28
| | | | Task-number: QTCREATORBUG-1600
* Debugger languages are now runconfiguration dependentLasse Holmstedt2010-09-011-21/+23
| | | | | | | | | | | There's a UI in qml/customexec/cmake/qmake run configs for choosing the debugger languages (C++ and QML). The default for all except .qmlproject is only C++, so default debugging behavior is the same. However, if the user wants to do simultaneous debugging with two languages, or only debug QML, they can select the languages from Run Settings and it will be remembered. Reviewed-by: hunger
* debugger: code cosmeticshjk2010-09-011-29/+32
|
* Debugger: Removed unused methodsLasse Holmstedt2010-08-311-25/+0
|
* Debugger: Disable auto switching of debugger languages based on qmlfilesLasse Holmstedt2010-08-311-4/+3
|
* Debugger UI: Removed debug language detection on mode changeLasse Holmstedt2010-08-311-12/+0
| | | | | It did more harm than good. Now, the auto detection is only done on run control change - this is something that Creator could also remember.
* DebuggerUI: Language selection mutual exclusive if lang is deselectedLasse Holmstedt2010-08-311-2/+11
|
* debugger: partially rever Qml&C++ action enabling logichjk2010-08-301-1/+2
|
* Debugger UI: Don't switch layout while debuggingLasse Holmstedt2010-08-271-13/+17
| | | | Reviewed-by: hjk
* Debugger UI: Fixed wrong debugger appearing if no editor is openLasse Holmstedt2010-08-271-2/+2
|
* Debugger UI: Don't write QML settings if QML debugging is disabledLasse Holmstedt2010-08-251-10/+14
|
* Debugger UI: Fix crash if QML plugin is not presentLasse Holmstedt2010-08-251-2/+5
|
* Debugger UI: Don't check "C++" language if active project is .qmlprojectLasse Holmstedt2010-08-251-1/+10
|
* Debugger UI: create initial settings for mainwindowLasse Holmstedt2010-08-251-0/+10
|
* Qml Debugger: Code style and cleanupLasse Holmstedt2010-08-241-55/+74
| | | | Reviewed-by: hjk
* Qml Debugger: Enable debugging qml+cpp standalone applicationsLasse Holmstedt2010-08-241-157/+381
| | | | | | | | | | | A new debugger engine, QmlCppEngine, is introduced, which wraps gdb and qml engines into one. Alternatively, if using Windows, Cdb is used instead of Gdb. Most of the debugger ui switcher is now rewritten, and it is tailored for the QML and CPP layout case, the only one supported anyway. Reviewed-by: hjk
* debugger: show all dockwidgets in the views menu, even if disabled.hjk2010-08-111-14/+15
|
* Merge remote branch 'origin/2.0'Friedemann Kleint2010-08-061-2/+7
|\ | | | | | | | | | | | | Conflicts: src/plugins/debugger/debuggeruiswitcher.cpp src/plugins/git/gitclient.cpp src/plugins/qmlprojectmanager/qmlprojectapplicationwizard.cpp
| * QML Inspector: Disable debug actions when qml inspector is disabledLasse Holmstedt2010-07-291-0/+5
| | | | | | | | Reviewed-by: Thomas Hartmann
* | debugger: remove unneeded code from ui switcherhjk2010-07-221-12/+8
| |
* | Fix consistency issue with splitter in debug mode.con2010-06-301-4/+16
| | | | | | | | Task-number: QTCREATORBUG-598
* | Core::Context: remove special handling of C_GLOBAL_ID/C_GLOBALhjk2010-06-281-7/+4
| |
* | Core::Context: compile hot fix for Windows.hjk2010-06-251-2/+1
| |
* | core: use a class derived from QList<int> instead of a QList<int> for ↵hjk2010-06-251-9/+7
| | | | | | | | | | | | | | | | Core::Context A mostly mechanical change. Reviewed-By: con
* | debugger: The DebuggerEngine refactoring.hjk2010-06-221-7/+24
|/ | | | | | | | | | | | | | | | | 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).
* Rename IPlugin::shutdown --> IPlugin::aboutToShutdowncon2010-04-281-1/+1
| | | | Discussed-with: hjk
* Use south tabs in the debuggerJens Bache-Wiig2010-04-261-1/+0
| | | | | | | | | | The current northpointing dockwidget layout looks broken since we repeat the label when the docks are unlocked. We also dont line up properly with the header sections. Other dock widgets in designer are also using the south tab so this would be more consistent. Reviewed-by: danimo
* Move the Debugger/Designer view menus to Window menu.Friedemann Kleint2010-04-201-33/+19
| | | | | | | | Move actions into FancyMainWindow. Register them in DebuggerUISwitcher and FormEditorW. Manually hide Debugger actions for Non-Debug modes (as they belong to the language context). Acked-by: con
* Added debugging mode for simultaneous QML and C++ debuggingLasse Holmstedt2010-04-151-0/+3
| | | | | | | | | | It's not yet possible to attach to an external app running a qml debugging server, because the server is only started on startup if an env variable is set. Changing this requires action from Brisbane, but even the current solution works for C++ apps with QML in them. Task-number: BAUHAUS-585 Reviewed-by: dt
* Fixed warning messages on close if user does not have QtCreator.iniLasse Holmstedt2010-04-081-0/+1
| | | | | Task-number: QTCREATOR-202 Reviewed-by: hjk
* debugger: some gui & code cosmeticshjk2010-04-061-9/+7
|
* Debugger[CDB]: Handle debugger warnings correctly.Friedemann Kleint2010-04-061-0/+1
| | | | | Prevent window from popping up repeatedly on warnings. Task-number: QTCREATORBUG-1061
* Fixed crash with debugger when qml inspector is not enabled as pluginLasse Holmstedt2010-03-261-1/+4
|
* Fixes: Tooltips for hover help didn't show up anymore.con2010-03-231-4/+0
| | | | Reviewed-by: Thorbjørn
* Introduced a single convenient function for updating additional contextsThorbjørn Lindeijer2010-03-231-7/+1
| | | | | | | | While before you had to call add, then remove for each context id and then call update, now you call updateAdditionalContexts with a list of contexts to remove and add. It has the update step built in. Reviewed-by: con
View Lorry Controller Status