i've updated a new version that i hope will fix the recent opera thing that i broke in last version, give it a try; seems to work on opera now (i was doing a test to make sure the window existed before capture and for some reason opera was tricking it). 2.09.09, let me know if it works for you:
http://www.donationcoder.com/Software/Mouser/screenshotcaptor/downloads/ScreenshotCaptor.exe

you don't have to reboot on upgrade, just make sure it's not in the tray at the time you install new version over old.

Capture Object with Autoscroll Now, does not seem to be working with the Mozilla (Suite v1.7.12) browser.

The only thing it picks up is the current screen.

It does work with IE.

Screenshot Captor v2.09.09

-------

MiniCap v1.01.02 also does not work with Mozilla.

It would be great to have a stand-alone MiniCap!

-------

Neither program Autoscrolls with Mozilla Firefox.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060112 Firefox/1.6a1

yep - mozilla is doing something different.. i'm working on it.  thank you with the report.
carol what mode did you use to scroll firefox with snagit?

if there is interest i will make a tiny little minicap program available as a standalone tool.

uploaded minor new version (2.09.10) which can now scrolling capture mozilla (make sure you are not in an edit box when you engage the shift+ctrl scroll capture or it wont work).

Thanks that works fine in Mozilla now.

A couple of further thoughts:

Strange behaviour with XDesk persists though. Is it possible to contact the author of XDesk to see where the conflict may lie. What happens is that when you initiate a scrolling capture (shift + rt. ctrl) the XDesk preview of the multiple desktops pops up from the system tray and interferes with the capture. The results are unpredictable including an occasional good capture, a black screen capture (just a black block) to a partial capture with repeats of a section going off to the right.

Is the algorithm of how the window scrolled in the library package or do you actually initiate the scrolling. It just doesn't seem to be very efficient. For example a screen requiring a single down scroll (ie. effectively a Page Down) flickers and flashes like mad, and pages that are larger in both x and y directions than the screen area seem to take quite a log time to render. It's not actually a problem as it works but it is a little disconcerting to see the page flipping about and blanking out like its on speed for 15-20 seconds.

The Red tooltip at the top of the redbox - I mentioned this before but I don't know if you saw it ... would it be possible to have that appear inside the rectangle so that it is visible when the item to capture is filling the whole screen.

option to have captionbar inside the box is a very good one, i will make that an option.

That's great - thanks

xdesk interference - that sounds like you've identified the problem; maybe i can contact author and see if anything can be done.  no way to disable the xdesk previewer temporarily i suppose?

I have disabled QuickView altogether (it is the part of the app that shows thumbnails of the active desktops) and can live without it for the moment.

For some reason the redbox capture must be issuing a Win+Q key stroke in the background to pull up the QuickView windows. Can't think why though.

Quote

Is the algorithm of how the window scrolled in the library package or do you actually initiate the scrolling. It just doesn't seem to be very efficient.

this is all done by my code but it's quite necesary.  there is no simple way to capture scrolling windows - what has to be done is one has to mark up the image and then send scrolling commands and then look for your marks in the new window, to see where you marks has moved.  snagit uses a much more subtle marker - you can probably notice some dots on your window if you look closely while snagit scrolls.  i may try to use more subtle marks in the future after we know everything else is working right.  maybe i should call it epileptic capture mode until then?

I can see why you would need to do that but I tried a capture of this webpage and it took over 15 seconds to complete and scrolled the window about 4 times plus a lot of intermittent flashing where the page didn't seem to move ???

just a note; on a test i just ran capturing this page, horizontal and vertical scroll needed,
screenshot captor took 13 seconds, snagit 21 seconds.

a test which involved no horizontal scrolling had this reversed.
with screenshot captor taking 20 seconds and seeming to get stuck temporarily at bottom, and snagit taking only 12.
another test had sc doing it in 11 seconds.  i think the first time an animation on the page confused it - i might be able to tweak that so it's not fooled by such stuff.