Ref T650, using FSX SimulatedObject type decrease exeption counter when successfully added

* normally adding the SimObject fails first,
* then the workaround is used (but exception counter is 1)
* this means a 2nd time the object cannot be changed, as there is already a counter number > 0
This commit is contained in:
Klaus Basan
2019-05-25 17:10:35 +02:00
committed by Mat Sutcliffe
parent 7e4ba2d1cf
commit c1ffad33bd
2 changed files with 6 additions and 3 deletions

View File

@@ -250,6 +250,9 @@ namespace BlackSimPlugin
//! Increase adding exception
void increaseAddingExceptions() { m_addingExceptions++; }
//! Decrease adding exception
void decreaseAddingExceptions() { if (m_addingExceptions > 0) { m_addingExceptions--; } ; }
//! Adding and directly removed
int getAddingDirectlyRemoved() const { return m_addingDirectlyRemoved; }

View File

@@ -1006,9 +1006,9 @@ namespace BlackSimPlugin
if (simObject.isConfirmedAdded() && simObject.getType() == CSimConnectObject::AircraftSimulatedObject)
{
const CStatusMessage soMsg = CLogMessage(this).warning(u"Confirm added model '%1' '%2', but as '%3'") << remoteAircraft.getCallsignAsString() << remoteAircraft.getModelString() << simObject.getTypeAsString();
this->triggerAutoTraceSendId(); // trace for some time (issues regarding this workaround)
Q_UNUSED(soMsg);
CLogMessage(this).warning(u"Confirm added model '%1' '%2', but as '%3'") << remoteAircraft.getCallsignAsString() << remoteAircraft.getModelString() << simObject.getTypeAsString();
this->triggerAutoTraceSendId(); // trace for some time (issues regarding this workaround?)
simObject.decreaseAddingExceptions(); // if previously increased and now working, reset
}
}
while (false);