Debugger: Minor visual tweak in VariablesView.
- Expression evaluation results are now highlighted as changed when they're first added, since they're immediately of interest, unlike uninitialized variables that're first coming into scope.
This commit is contained in:
@@ -515,10 +515,19 @@ private:
|
|||||||
void _CompareValues()
|
void _CompareValues()
|
||||||
{
|
{
|
||||||
fValueChanged = false;
|
fValueChanged = false;
|
||||||
if (fValue != NULL && fPreviousValue.Type() != 0) {
|
if (fValue != NULL) {
|
||||||
BVariant newValue;
|
if (fPreviousValue.Type() != 0) {
|
||||||
fValue->ToVariant(newValue);
|
BVariant newValue;
|
||||||
fValueChanged = (fPreviousValue != newValue);
|
fValue->ToVariant(newValue);
|
||||||
|
fValueChanged = (fPreviousValue != newValue);
|
||||||
|
} else {
|
||||||
|
// for expression variables, always consider the initial
|
||||||
|
// value as changed, since their evaluation has just been
|
||||||
|
// requested, and thus their initial value is by definition
|
||||||
|
// new/of interest
|
||||||
|
fValueChanged = dynamic_cast<ExpressionVariableID*>(
|
||||||
|
fVariable->ID()) != NULL;
|
||||||
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user