I'm going to think on it some tonight and will probably try a couple of things tomorrow or the next day. My working theory of what the problem is : When using the COM API in Snagit we take a lot of precaution to not overwrite existing settings in Snagit so that you could use the COM API and not have it mess up the Snagit UI and those extra precautions might be a bit too aggressive while doing a delayed capture. Connection attempt failed with 'EAINONAME - Neither nodename nor servname provided, or not known'. I've spent some time reviewing the code involved in Snagit and I haven't pinned down a good way to fix this yet.
If that isn't working for you with the latest 13.1 release of Snagit, let me know the exact screen capture settings in MM that you are seeing trouble with. Refer the link How do I reset Windows Update components to reset Windows Update components. Method 2: Reset Windows Update components and then check how it works. Refer the link Troubleshoot problems with installing updates in Windows 7 to run the troubleshooter. If I use a capture delay through the Snagit UI ( by creating a new profile that has a 5 second delay ), it works fine, but if I do the same from the COM API, everything falls apart and the code path taken isn't right.Ī workaround to use Snagit 13 with MM is to set the capture delay to 0, that is working well for me. Run the Windows Update troubleshooter to diagnose the exact issue. I have verified what you already know and that is that it is related to the capture delay.
0 kommentar(er)
