Screenshot Captor use problems

[klk]

Hi
I posted my problem yesterday 2/11/09, but now I can't find my post. So, I am repeating my problem. I installed V2.44.01 and I am now getting frequently an error box saying 'Invalid floating point operation'. Sometimes this error message starts to berserk and repeat itself all over my PC screen, till I stop it using Task Manager. The icon in the system Tray shows red in the screen area.

I never had such problems with any of the earlier versions of Screenshot Captor.

klk

[mouser]

Does the error occur after you perform some particular action? or on startup?

It sounds like perhaps one of your options may be set strangely somehow.

Can I suggest you try this:

• Exit ScreenshotCaptor from tray if it is running
• Move the ScreenshotCaptor.ini file in the Screenshot Captor program directory someplace safe for backup
• Restart ScreenshotCaptor -- when it finds the option file missing it will recreate it with default settings.

See if that fixes the problem.  If so -- could you send me the bad options file you moved so i can see if i can reproduce the problem?

[klk]

Does the error occur after you perform some particular action? or on startup?

It sounds like perhaps one of your options may be set strangely somehow.

Can I suggest you try this:

• Exit ScreenshotCaptor from tray if it is running
• Move the ScreenshotCaptor.ini file in the Screenshot Captor program directory someplace safe for backup
• Restart ScreenshotCaptor -- when it finds the option file missing it will recreate it with default settings.

See if that fixes the problem.  If so -- could you send me the bad options file you moved so i can see if i can reproduce the problem?

-mouser (February 12, 2009, 02:46 PM)

Hi
I uninstalled it and reinstalled..but the problem persists. I moved the ini file out and did what you said. The only preferences i set are copy to clipboard, start minimized and show main form. The problem appeared(Invalid floating point operation). I repeated your instructions with the ini file again. This time I only set the one option...show main form. And the same problem appears. If I understand it right, this option opens up the application, instead of the default choice dialog box.
I'm running WinXP Pro with Sp3.
klk

[mouser]

When does the error appear -- on program startup or when you try to capture, or when?

[klk]

When does the error appear -- on program startup or when you try to capture, or when?

-mouser (February 12, 2009, 04:22 PM)

When I do SHift PrScr and try to do screen capture

[lanux128]

klk: are you using a non-English or European locale in Windows? maybe the floating point error appears due to misinterpreted decimal point <tt>,</tt> with <tt>.</tt> or vice-versa.

[klk]

klk: are you using a non-English or European locale in Windows? maybe the floating point error appears due to misinterpreted decimal point <tt>,</tt> with <tt>.</tt> or vice-versa.

-lanux128 (February 12, 2009, 08:09 PM)

Hi lanux128
No, I am right here in the good ol' US of A(Upstate NY to be specific) and using the English(USA) locale in Windows.
klk

[Phil White]

Hi,

I can certainly confirm the berserk 'Illegal floating point operation ' when capturing a selected region (Shift + PrtScr). It doesn't happen with every capture. I have only had it happen about 10 times in 500 captures.

I'll have to take more notice when it happens again, but I believe most times it occurred when I was selecting the region and changed my mind about where to start. Something I then did (what??? I don't know) caused the problem.

Phil White

[mouser]

selected region capture - ok that's a big clue.
klk -- does the problem ever happen when doing other kinds of captures?

and to confirm -- it happens AFTER you select the region to capture and capture initiates?

[klk]

selected region capture - ok that's a big clue.
klk -- does the problem ever happen when doing other kinds of captures?

and to confirm -- it happens AFTER you select the region to capture and capture initiates?

-mouser (February 14, 2009, 08:25 AM)

I have always used this Shift PrScr since that is my most favorite method....I like to screen capture only areas I like, not the whole screen. I have not tried other modes with this latest version, but have done with the previous versions where I have not encountered any such problems. Unlike Phil's situation of 10 instances in 500, mine occurs almost every other one or even consecutively.

klk

[mouser]

ok well with this new info, let me see if i cant figure out the cause.

[Phil White]

Hi,

After a bit of testing, I can repeatably produce the error by selecting ... Capture - Grab selected region and then DOUBLE clicking on the top left corner of the region I want. This possibly gives rise to an untrapped divide by zero condition when scaling.

This is consistent with my saying I thought it happened when I changed my mind... I probably clicked on the same spot a second time.

Hope this helps

Cheers
Phil White

[mouser]

working now on some long-overdue fixes to region capture (escape to cancel, full desktop selection not just current monitor) and will try to find this error as well.

[mouser]

Can you guys (and anyone else who wants to check out the new region capture features), try:
https://www.donation...nshotCaptorSetup.exe

v2.47.01 BETA - February 15th, 2009

• Attempting to make all region and object capture modes work better on multimonitor setups; no need to activate from desired monitor.
• Adding ability to abort region captures with escape key.
• Trying to skip the cleared screen message which used to show on saving image.
• [Bugfix] Trying to eliminate floating point error some were seeing on region capture.
• [Bugfix] Main form could stay hidden even when there was a pending overwrite/cancel/save dialog trying to be shown.

[Phil White]

Thanks for the update

Everything appears to be working properly on a three monitor setup. This means that I no longer have to use the work-around of moving the ScreenCaptor window to the monitor on which I wanted to do the captures. Way better!

The bugfix worked for me in that I couldn't reproduce the error by double clicking as before.  As I was only getting the error intermittently, I will keep checking as I do more captures over the next week or so.

I notice that double clicking now closes ScreenCaptor. I personally would like to see the ScreenCaptor window re-opened as the double click is obviously a mistake and you usually want to do another capture.

Cheers
Phil White

[mouser]

I notice that double clicking now closes ScreenCaptor.

can you explain what you mean?

[Phil White]

Open the ScreenCaptor window
Capture - Grab selected region
Move to the first corner of the capture and get the cross cursor

Now if you double click by mistake (which used to produce the illegal operation) instead of click and drag to select the region, I would like the ScreenCaptor window to reopen so that you could select your capture again instead of closing to the system tray.

It is really only a minor point and the way it is now only requires one more click to reopen it.

Cheers
Phil White

[mouser]

ok i understand -- i will try to have sc go back to whatever state it was before capture.

[klk]

Can you guys (and anyone else who wants to check out the new region capture features), try:
https://www.donation...nshotCaptorSetup.exe

v2.47.01 BETA - February 15th, 2009

• Attempting to make all region and object capture modes work better on multimonitor setups; no need to activate from desired monitor.
• Adding ability to abort region captures with escape key.
• Trying to skip the cleared screen message which used to show on saving image.
• [Bugfix] Trying to eliminate floating point error some were seeing on region capture.
• [Bugfix] Main form could stay hidden even when there was a pending overwrite/cancel/save dialog trying to be shown.

-mouser (February 15, 2009, 02:54 AM)

Just installed this Beta version. So far the problem has not appeared. Hopefully, it is fixed for now. Other things seem to work fine. Tnx...klk