Startup Movie Locks Up Preview - RC2

[AXXESS]

I am using a 320x240 Flash movie as the startup movie for a current project. The movie is just a 5 second still being used as a splash image.

Under the "Startup Movie" menu, I have set the window size and the media size as "custom" to match my movie size of 320x240. I am using the border.

When previewing the project, the Flash movie shows, and the preview locks up HARD. No shutting down with the Task Manager either.... the movie will not go away until the PC is rebooted.

When this is going on, the orange IR disk logo is present in the taskbar for the preview, but no text. Right clicking on it will not allow me to close it.

Something I'm missing.... or a problem??

[Darryl]

I believe I know what the problem is in this situation:

For the Flash Startup Movie, there are two ways to have it "end" and continue to your application:

1) Enable the "Allow Click to Skip" option.
2) Fire a "quit" FSCommand in your Flash file to let AutoPlay know when it's done.

I'll submit a report about not being able to exit in Preview mode though.

Hope that helps. If that is not the case, post back with further information.

[AXXESS]

The "click to skip" does work, but I don't want to use that.

OK, I can fire an FSCommand from the startup movie.... but where to set up the action to listen for it to initiate the page jump?

[Darryl]

If I understand your question correctly, you don't need to put any action into AutoPlay in order to exit the Intro. AutoPlay will automatically respond to a "quit" FSCommand that is fired any time in your Flash file. Once that is detected, it will automatically close and show your first page.

Hope that makes sense.

[AXXESS]

Thanks for the info Darryl.

I was using "quit" as an FSCommand but apparently it needs to be used as an argument to have AutoPlay pick it up automatically without setting up actions to listen for it.

[Ted Sullivan]

Hi Axxess,

If possible could you provide us with the flash script that you are using the sent the FSCommand?

[AXXESS]

Hi Ted

It is just a 55 frame movie (at 12 fps) of a still image in Swish.

On frame 55 I have the following script:

onFrame (55) {
fscommand ("quit","quit");
stop ();
}

When using it as ("quit", ""); it wasn't working. Once "quit" was set as the argument all was well.

[Darryl]

What happens if you just have:

fscommand ("quit");

instead of specifying an argument?

I'm by no means a Flash guy, so Corey may want to jump in on this one. We'll certainly adhere to whatever method makes the most sense. But I would like to know if the above method works.

[AXXESS]

What happens if you just have:

fscommand ("quit");

instead of specifying an argument?



With Swish you have to have the second set of quotes for the argument (the script cannot be manually typed in Swish).

So it still looks like this...

onFrame (55) {
fscommand ("quit","");
stop ();
}

But now it works in this manner. Maybe I "fat fingered" it before when typing "quit"....

You know... quiet, quite, quixote....:rolleyes:

[MadNav]

Day before yesterday I encountered the hang/freeze lockup with AMS5RC2 .. same deal as previously posted.

Always locks/hangs when using the 'browse files' button within the properties of an object/page/project.

This last time it happened while trying to find/select a startup movie clip. The problem is generic to the 'browse files/folders' and very next to impossible to recreate. But I loose all work even to include the 'Auto-save' functionality.

I have been having some intermittant issues with a very small handfull of websites/services recently and resolved all of those issues by going to this link:

http://msdn.microsoft.com/library/default.asp?url=/downloads/list/webdev.asp

and repairing my windows script engine. I have not seen the issue return at all no matter how hard I try. My gut reaction after trying so hard to hang/freeze the app after this is that this is the culprit.

Does this make sense I.R. ?

[Corey]

fscommand ("quit") is one of the native fscommands understood by the standalone version only of the Flash Player, like allowscale, etc.

If you use it in the standlone player it will cause the movie to exit (therefore no point in having any actions after that) the same way Application.Exit() does in AMS. If you use it in anything other than the standalone flash player nothing will happen unless you have set it up to detect that particular fscommand...

So I assume the guys have it set up to detect that fscommand. Therefore it should work. Hope that helps...

As far as a fix goes perhaps once Ted can see your file they can figure out what's not happening... I am not familiar with "onFrame" this is the first time I've seen it so I'll have to look into that in order to make an accurate assessment of what might be going wrong... I assume that is Swish native function, I'll update you if I find out anything.

Corey Milner
Creative Director, Indigo Rose Software (http://www.indigorose.com)