Okay. That's what I was trying to establish. You seemed to indicate that you might be trying to capture an application window that was maximised to full screen on monitors running high resolutions, but I wasn't quite prepared to believe it. I realise that you may only be starting out with using Captivate for screen capturing so I'm going to offer some suggestions that should make your life a lot easier. Unless you have an impelling reason for capturing at such large window sizes (e.g. you KNOW that all of your target audience WILL be using similar monitor resolutions, AND you cannot display the captured application at anything less, AND delivery bandwidth is NOT an issue) then I would suggest you aim for something much smaller. You really don't need to capture at full screen. There's no advantage to it, and as you've discovered, there are heaps of disadvantages. You just cannot predict how the edges witll turn out consistently enough to enable you to go back and add more screens at a later date. They just won't match. This isn't Captivate's fault. It's just not a good strategy to use. The better way to go is to decide up front what the MINIMUM practical size should be for your final output and then set your Captivate project up at those dimensions before you start capturing. For example, even though I also run dual monitors at 1920 by 1200 pixels, I never capture at anywhere near that size. If I'm doing tutorials to teach Captivate 5, I'll choose something around 1260 pixels wide by about 630 high and set my project to that. Then I'll use the capture option to snap the target application into my project size. So you make your application fit your project, not let your application or maximum monitor size determine how big your project should be. You need to remember that many people will not be using resolutions as high as yours. If you build your tutorial too large, they won't be able to see all of it, and if it's too high, they won't be able to get to the playbar at the bottom to control the movie. So one of the first things you need to get sorted BEFORE capturing anything on a project is who the target audience is, and what their minimum monitor resolution will be. Then you still need to allow a margin for "browser chrome", browser toolbars or title bar, and cut it down even further on the height dimension to allow for the playback bar controls. So even if you DO happen to have a target audience that are all on 1440 x 900, by the time you allow for all the things that cut into your screen real estate, you might find you need to capture at around 1420x800 or less. Is this making sense?
... View more