Skip to main content
A
Anonymous
January 22, 2008
Question

Flash with multiple links on a slide

  • January 22, 2008
  • 1 reply
  • 273 views
I'm working on a complex project consisting numerous modules where some slides in each module have many options a user might take. He is then directed to the appropriate slide which is usually but not always in the same module. In order to make the slicing of modules as efficient as possible it would help to understand what Flash is doing when it reaches a slide where there are several options. I guess that if there is only one option it begins downloading the next slide as soon as the current one has arrived. When there are multiple options does it wait for the user to make a choice before it fetches the next slide, or does it fetch all the possible target slides? And if it's the latter, on what is the decision which one to get first based?

Wicked Wizard
    This topic has been closed for replies.

    1 reply

    Captiv8r
    Captiv8r
    Legend
    January 22, 2008
    Hi Wicked Wizard

    Unless you have structured your project so each click box loads up a different project (Flash Output .SWF), most or all of the existing project should be loaded into memory. Captivate does not load slides on an individual basis.

    You could be seeing a result of preloading loading up 60% of the project and starting. And if you have a Click Box or Button object that points to a later slide toward the end, it won't work immediately because the movie hasn't completed that part.

    Maybe this is the case?

    Cheers... Rick
    A
    Anonymous
    January 23, 2008
    Ah, so maybe I've misunderstood something earlier. I'm thinking of a project being streamed over http - obviously an exe file needs to be fully downloaded and then loaded by the local PC before it runs, but if it's a streaming Flash movie I understood that it starts to display as soon as there is enough on a remote user's PC to permit that. Which is what gave rise to my question.

    Originally this was one enormous project, and I divided it up partly for management and maintenance reasons, partly because at run time some links were to slides a long way away and took an age to load, far longer than the web site I am building a demo for. My initial review versions were published as exe files for convenience, but the final version will be SWFs. and it's those that I'm testing now.

    But I can see there are benefits in having smaller SWF files too, if a link to a different project needs that project to download fully before it will run.

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