Is there a limit on the number of Variables and Conditional Advanced Actions?

hi all,

 

does have data on whether there kind of design limitation on number of user variables or conditional actions can built single captivate module?

 

i'm working @ client site using captivate 5.5 on windows xp. course i'm building complex software simulation requires lots of dynamic behaviour driven user variables , conditional advanced actions.

 

i seem recall hearing somewhere on forum users finding if exceeded 200 variables, captivate start crashing.

 

i've reached 196 user variables , 90 conditional advanced actions on 1 particularly complex module.  proceeding until afternoon, captivate 5.5 has crashed 3 times on me while editing complex conditional advanced actions.

 

so have 'hit wall', or there can work around limitations? (i've cleared cache still crashed once after that.)

hi rod,

 

first want "thank you" awesome support give captivate community , forum.

 

i don't have data, have suggestion:  use javascript offload of variables , advanced actions.  why javascript help?

1. it reduce number of advanced actions , captivate variables might need in .cptx project.
2. memory management during runtime.

 

when viewing course in browser, have 2 virtual machines (vms) @ disposal.  flash vm , browser's javascript vm.  leveraging 2 in combination can give bit of "load balancing" when comes to memory management and garbage collection.  if can accomplish majority of logic in javascript, i'd go route because believe javascript more forgiving when comes garbage collection flash vm.  every cp variable create , advanced action uses variables consume memory computer during design time , runtime... needless it's critical leverage 2 vms when you're pushing limits of software.  ever wonder why when create cp variable, captivate asks enter number of characters need display variable?... control amount of memory needed project.  when you're pushing limits, take @ cp variables ensure they're not utilizing more memory need.

 

however, there cp actions can't javascript show/hide other cp elements, or enabling or disabling cp objects.  part of challenge figure out work best using javascript vs. advanced actions & cp variables in captivate.

 

i avoid advanced actions if possible.  if you're creating project client, may not have necessary javascript expertise maintain project once hand over.

 

best,

 

jim leichliter

More discussions in Advanced Adobe Captivate Users

adobe