Our current template (in version 5.5) is 800x600 and it is too small for all of our content consumers. We originally went with that size to be sure to accommodate all screen sizes, but with the move to Captivate 6 (we just got our licenses) and a fresh re-do of our template and theme standards, it's time to re-think our project size.
Our internal employees use either:
- Laptop display of 1600x1050
or
- Varies, but many are still on 1024x768 displays (often dual displays); others are on 16:9 aspect ratio monitors with higher resolution
Our external customers can potentially be on any resolution, but I am okay with cutting out the 800x600 display people. Time to move on from them : )
My thinking currently is to go with a project size default of 990x600, which allows for ~30 pixels for the playbar underneath and does NOT include the TOC. So for those on the older 1024x768 displays, the TOC will have to be scrolled away from, which is not ideal.
One other idea is to figure out if there is a way to set the html wrapper to auto-scale the content so that this isn't such an issue. Articulate Presenter does this out of the box - why does Captivate not? Regardless - what size do you publish to, and why? I've found over the years that 800x600 is a real hassle for screen captures of anything but the most simple of applications for demonstrations/sims.
Rod,
Thanks so much. One concern is the TOC. Our user feedback has always been positive on the TOC being visible at all times on the left. But, as you know, it adds 250px to the width. I just found out last night that Captivate 6 now has the auto-scaling feature that Articulate has had for years. While it doesn't scale nearly as nicely as Articulate's player does, it's still a huge step forward.
North America
Europe, Middle East and Africa
Asia Pacific