> Andreas wrote:
>> what is the Layer(int) option in the axShockwave.LoadMovie(layer, url)
> This sounds like you are actually talking about levels. Levels are like
> layers in html in that the higher the number the closer to the user from
> the screen they are, So it allows you to set a stacking order for content
> much like depths. The difference is that levels can have external swfs or
> non-interlaced jpegs loaded into them at run-time like a movie clip.
> Unlike a movieclip instance though levels use the origin of the main
> movieclip (main timeline). I've not seen any way to move the origin of a
> layer, but that is easily achieved by using the loadMovie method and
> loading the content into a named instance of a placeholder movieclip.
>> I load a movie with a comboBox in it, fill it, use it, ... all working
>> fine ... if I reload this movie, or load any other movie with a comboBox
>> component in it, into the axPlayer, (into the same layer that is) I get
>> the effect that the colored frame outline, drawn if you pull down the
>> menu [snip]
> This sounds like a problem I ran into recently when loading data from a
> xml file. The swf worked fine on it's own, but when I loaded it into
> another movieclip using loadMovie() the comboboxes would have the initial
> data but none of the rest. Or at least soon as I clicked on the combobox I
> would get just the green halo effect and no additional data.
> The solution that I found is to add the component to the library of the
> movieclip that you are loading the second movieclip into. It doesn't have
> to be on stage, just in the library. This will add to your main movieclips
> size though.
> I seem to recall that if the loadMovieNum() functiuon is used to load the
> swf into a level instead it gets arround this issue, but have yet to try
> it myself though I may in the near future.
> Brandon Bradley
> Macromedia Certified Instructor