saberbud/seer
1
0
Fork 0
mirror of https://github.com/epasveer/seer.git synced 2026-08-29 08:34:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add Ctrl+Shift+1 through Ctrl+Shift+0 hot keys.

Browse Source
This commit is contained in:
Ernie Pasveer
2026-01-11 17:03:40 -06:00
parent c2a1a39940
commit 655dd76959
2 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/SeerMacroToolButton.cpp
+6
View File
@@ -7,6 +7,7 @@
#include <QtWidgets/QMenu>
#include <QtWidgets/QMessageBox>
#include <QtGui/QMouseEvent>
#include <QtGui/QShortcut>
#include <QtCore/QTimer>
#include <QtCore/QSettings>
#include <QtCore/QFileInfo>
@@ -37,6 +38,11 @@ void SeerMacroToolButton::setMacroName (const QString& name) {
return;
}
// Add combination shortcut for re-open closed file (Ctrl + Shift + T)
QShortcut* shortcut = new QShortcut(QKeySequence(QString("Ctrl+Shift+")+_macroName[1]), this);
QObject::connect(shortcut, &QShortcut::activated, this, &QToolButton::click);
// Create the macro filename where the macro is to be written.
QSettings settings;
src/resources/help/BreakpointGdbSeerManager.md
+4 -4
View File
@@ -119,13 +119,13 @@ This input field allows GDB and GDB/mi commands to be manually entered. The resu
Seer maintains a history of N commands, as set in the Seer Config dialogs. This history is remembered for the next time Seer is used.
### MACRO gdb commands
### Macro gdb commands
There are 10 macros you can create for custom commands. They are labelled "M1" through "M0". Think of your keyboard with numeric
keys 1 through 0. They have hotkeys mapped from Ctrl+Shift+1 through Ctrl+Shift+0. Clicking the button or usinging the hotkey will
execute the commands in the macro. Holding down the button will bring up an editor to edit the contents of the macro.
keys 1 through 0. They have hotkeys mapped from Ctrl+Shift+1 through Ctrl+Shift+0. Clicking the button or using the hotkey will
execute the commands in the macro. Holding down the button will bring up an editor to edit the contents of the macro.
Typically the macro contains gdb commands or gdbmi commands. Output will go to the GDB output tab. The macro is executed using gdb's
Typically the macro contains gdb commands. Output will go to the GDB output tab. The macro is executed using gdb's
"source" command, which can handle a lot off unique cases.
### References