We can't resource this. What version of TurboActivate are you using? Use the latest version and try again.
TA_GetHandle() call generates "Debug Assertion Failed"Solved
kitaekI am using static lib (TurboActivate-MTd.lib), in VS2010 C++, with MFC for a windows app. I get a debug assertion on the very TA_GetHandle() call with debug version only. On the release version (TurboActivate-MT.lib), this does not happen.
on the assertion, it gives "vector subscript out of range" as a message, and "c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\vector" as a file, and "932" as a line.
the same TurboActive.dat file works for the release version. and if I remove the TurboActivate.dat file from the debug directory, TA_GetHandle() call passes with return value of 0, in both debug and release.
any idea???
kitaekhow do you check the version number on the static library?
anyways, I just downloaded "TurboActivate-static-VS2010.exe" on 2/28/2017, and its file version is 16.4.0.0, and the TuroActivate-MTd.lib creation date is 1/17/201(date modified).
the "TurboActivate.exe" and "TurboActivate.dll" I downloaded on the same date has the same date stamp, and version number is 4.0.9.3
kitaekthe latest static lib I can download is 4.0.9.3, yet the main package is 4.0.9.4.is there any plan to update the static lib packages?
still be debug version asserts with message :vector subscript out of rangeline:932file:c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\vector
>> "the latest static lib I can download is 4.0.9.3, yet the main package is 4.0.9.4."
the only change between TA 4.0.9.3 and 4.0.9.4 was an updated VBA poject. None of the binaries were touched. Hence no new static library release.
>> "I am using static lib (TurboActivate-MTd.lib), in VS2010 C++, with MFC for a windows app. I get a debug assertion on the very TA_GetHandle() call with debug version only. On the release version (TurboActivate-MT.lib), this does not happen."
We cannot reproduce this here. We've tried our example project in VS 2010, with the currently released static libraries. And we tried both the x86 and x64 versions (both in debug and release modes). No crashes or assertions anywhere to be found.
Can you try the example app? Do you get an assertion?
kitaekwell, it seems the problem goes away if I delay the call to the point after CWinApp class instantiation is complete.
calling the TA_GetHandle() and doing all others in CWinApp::InitInstance() implementation solved the issue.
maybe some initialization depends on something...........
anyways, now it works....
Great, I'm glad you figured it out.