Different slides size , same project

Question

Hi!
I would like to know how I can have slides with different sizes in the same project without loosing image quality?
When I import the slides into the master project the images become so small that I badly can read the slide, also all the actions I included in the previous project is lost when I import these slides. Anyone can explain how this works and how I could work with slides with different sizes on the same project.
Thanks

Answer 1

Resizing screencaptures in any way is almost guaranteed to result in loss of clarity.  If you've captured at a different screen size to the project where you want to copy and display the captures, and then resize the graphics to try and accommodate the new size, you will find that edges of on screen text in particular will lose crispness and become fuzzy.  Only when kept at exactly 100% of capture size will you be able to preserve full quality and crisp edges.  This is only usually an issue with screen captures of software interfaces where the original capture format was GIF, PNG, or BMP due to "lossless" compression. Graphics that began life as JPGs use a totally different "lossy" compression algorithm which is designed for working with gradients and shaded blends as is usually found in photographs.
Unfortunately, Advanced Actions created in one Captivate project file cannot be copied to another project file in current versions of Captivate.  However, this IS something we've requested for future versions of Captivate as more and more Captivate authors are discovering the power of Advanced Actions and want to share them across projects without having to recreate them each and every time.
If you know in advance that all modules in a particular elearning course will require specific variables or actions, the recommended workaround is to create a Captivate template (in advance) that is used as the starter for all modules.  This way, you don't have to create all of the actions from scratch each time.  However, this only works if you have done your preliminary design requirements quite thoroughly and know in advance exactly what Advanced Action functionality your projects will require.
I'd have to admit that I still haven't found a way to accurately anticipate such requirements in practice.  I tend to "discover" a lot of requirements for functionality during the course of the development that I never thought of at the beginning of the project.  But that's just me. Your mileage may differ.