Skip to main content
B
Brad55
Known Participant
June 18, 2009
Question

Captivate 4-file size

  • June 18, 2009
  • 2 replies
  • 774 views

I have some concerns about Captivate 4 in how it handles your project
file and its size.
I started with a clean slate and started a new project, recorded the
slides which was only 5 and saved the file. That file size was (1,035KB)
then I tried something I opened a new blank project and imported the
same file and saved it, once saved it was (728KB). Now for another
example a project was made in Captivate 2, so I opened the file and
Captivate wanted to do a conversion on it ok no problem. Now  file sizes
Captivate 2 (15,417KB) saved Captivate 4 (17,613KB) now for the mind
blowing version, I opened a blank project and did an import then saved
the file,  get ready for this file size (4,277KB). From what I am,
seeing is the Captivate keeps a record of everything that you do to your
project or it is not letting go of the file space.
1.      Why is there 2MB's more in a converted file from Captivate 2 to
Captivate 4 when for as long as I have been working with computer
programs as they go up in version number they have cleaner code and when
you pull a file into the newer version it cleans the old code out?
2.      How can there be so much of a deference between converting and
importing, from (17,613KB to 4,277KB) to me that's a major change 13MB
of trash in the file?

    This topic has been closed for replies.

    2 replies

    C
    commando_dhruv
    Participating Frequently
    June 19, 2009

    Hi,

    1)  File Sizes going up is understandable. Every Object has many visible( scripting support etc... ), and invisible NEW properties that are added in the newer versions.

         Also Captivate upgrade for this case will work like CP2 => CP3 => CP4. So there is a high chance something unnecessary gets added.

    2)  This simply means lot of work has been done on the import front of CP4

         Note that projects made in CP2 has many unreachable nodes, so unles CP gives a repair feature it would be costly to check what nodes are unreachable while opening/saving. So CP keeps loading and saving these useless nodes.

         This problem is absent in import since you cannot import the unreachable node.

    I have tried to keep it simple, but let me know if you need more details.

    --

    Manoj

    Captiv8r
    Captiv8r
    Legend
    June 18, 2009

    Hi there

    Hopefully one of the Captivate Developers will pop in on this and provide some technical details when they wake.

    (My Google Status Bar Clock is indicating it's currently 4:21 AM in India, so I might assume they are all fast asleep.)

    Until this happens, I'll only speculate that while it's true that many software applications store data in a more efficient format with upgrades, Captivate has added many different features in version 4 than what version 2 offered. My guess is that there are probably internal cubbyholes that have been created to manage the new features. But that's just a total guess on my part.

    Cheers... Rick

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices