- Messages
- 24
- Country
-
Almost all calls in SimConnect have two or three ways in which they can return a result to the caller:
Any ideas on what the best approach is here? If possible I'd like the call to end when I know no exceptions have been returned, but that means either a delay, which flies against all principles (because... for how long?), or else spend that extra call and wait for the (changed) data.
Cheers,
Bert
- The call itself can fail, which generally means that required values are missing or wildly incorrect. An obvious example is an incorrect HANDLE.
- The call can fail validation by the simulator, resulting in an exception message. This is always linked to a "SendID", which has to be queried after performing the call. Why it is not returned always is a mystery to me, because zero or negative values are errors, so positive values could have been used as success marker and SendID in one.
- Depending on the call, a reply message (or stream of messages) comes in, generally using a RequestID.
Any ideas on what the best approach is here? If possible I'd like the call to end when I know no exceptions have been returned, but that means either a delay, which flies against all principles (because... for how long?), or else spend that extra call and wait for the (changed) data.
Cheers,
Bert