Archived and Closed
This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Forum maintenance: Posts with no replies, repeat posts, outdated posts, etc.
I am running the latest version (11.1.0 (Build 248) - Sep 7 2012 on WIndows 7 (Ultimate) with the latest MS updates installed.
I am developing a program (Visual Studio 2010, using C#) that has a window that I wanted to fully capture using SnagIt.
When the SnagIt capture started I selected the bottom right diagonal arrow to indicate I wanted the full underlying window.
SnagIt started to scroll the window.
The attempt to fully scroll the window triggered a program error in my C# program, which Visual Studio properly intercepted and dutifully opened a dialog box informing me of the error and waited for me to click on the 'Continue' button.
Unfortunately, the SnagIt scroll operation is done under a system-wide dialog mode so no data input is accepted in any window.
SO, I now had a deadly-embrace.
-- SnagIt was waiting for the scroll operation to complete
-- Visual Studio was waiting for me to click on the 'Continue' button
-- but I was locked out from clicking on it
-- I could not even get to the Task Manager to cancel anything
because Windows would not allow any input to any other window
The only way out was to boot the system (or hit Ctrl-Al-Del and log me off). Either way I lost valuable changes in other unrelated windows.
The problem is that SnagIt should use a timeout for the scroll and abort the operation if the scroll times out. That would have fixed the issue.
I think this is rare but a serious problem.
There are no replies.