G2Wait() timing out after G2Freeze()

Programming Questions
1

Hello,

According to this reply: https://forum.commonvisionblox.com/t/whats-the-best-way-to-handle-camera-disconnections-in-cvb/157/4 , calling G2Wait() after G2Freeze() will result in G2Wait() returning CVC_E_GRABABORTED.

This is indeed the behaviour I have observed while using CVB 13.02. However, since updating the version of CVB to 14.01, I find that calling G2Wait() after G2Freeze() always results in G2Wait() returning CVC_E_TIMEOUT.

May I ask if this change in behaviour is intentional?

Edit: To clarify, with both versions of CVB, I am using G2Freeze() with bKill = false.

2

Due to internal changes of the 2nd Gen Stack now using the 3rd Gen Stack internally starting with CVB 14.1, I assume that this behaviour was changed intentional. Or as a side effect of this change.

It is also more convenient to get a timeout error. An Abort error makes sense when G2Freeze is called during an already active G2Wait call.