Slide plays OK on its own but fails in project using cpInfoCurrentFrame in actions.

Question

Hi,
We are using the latest Captivate 8 with the latest patch...
The project is set to 10 fps to do the calculation easily.
So, I have a slide that is using the cpInfoCurrentFrame to set a variable (FirstFrameIn) to whatever the frame number is.
I then have a group of advanced actions that use this variable to jump back and forth on the timeline. They do that by adding the number of frames their content is away from to the (FirstFrameIn) and then jump off to that frame.
Layed out on the time line there is a submit for each block of content. The submit resets the value of the (FirstFrameIn) to a new block of content on the timeline and then jumps there to do the next block of user selections.
This works much like individual slides on one slide.
This example timeline explains the process.
This all works fine if the slide is run on its own. But the moment I run it in a project or with any other slide. The action code breaks into an nonsensical mess where buttons do whatever they choose to do.
Oh and another thing is my timeline vanishes from time to time.

Answer 1

Thanks Lilybiri,
I watch your example and read the article...Cheers. But my process is even simpler. I am using J'script to create an array that takes its text from a large text box that is not visible but has a particular name {TTbox_(put in what ever your slide number is to make it unique) } that is just touching the stage. The J'script references and separates the text based on an array position Newtext[num] - the num variable referenced in the array, increments based on the position of a pipe | in the initial text box it could even be a comma. I call and increment the array based on the new position in the timeline I then set the objects.text value in the J'script. Your example requires an Action script that has lots of ifs an else's. Mine only a num value based on the frame the timeline ends up on ( heaps simpler ). All I do is update the TTbox,The J'script can discern the difference between slides and objects. So, so long as you name the TTbox something like TTbox_3 the J'script figures the difference and discards the 3. It will reference new text for each new slide. Or you can just fill one slide with every bit of didactic needed.