Corrected bug with memory inspection panes not disabling the hex view widget in certain instances, when target execution is resumed
This commit is contained in:
@@ -159,15 +159,13 @@ void TargetMemoryInspectionPane::onTargetStateChanged(Targets::TargetState newSt
|
||||
using Targets::TargetState;
|
||||
this->targetState = newState;
|
||||
|
||||
if (this->activated) {
|
||||
if (newState == TargetState::STOPPED) {
|
||||
this->refreshMemoryValues([this] {
|
||||
this->hexViewerWidget->setDisabled(false);
|
||||
});
|
||||
if (newState == TargetState::STOPPED && this->activated) {
|
||||
this->refreshMemoryValues([this] {
|
||||
this->hexViewerWidget->setDisabled(false);
|
||||
});
|
||||
|
||||
} else {
|
||||
this->hexViewerWidget->setDisabled(true);
|
||||
}
|
||||
} else if (newState == TargetState::RUNNING) {
|
||||
this->hexViewerWidget->setDisabled(true);
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user