search

zzyycc / bulk-loader

Automatically exported from code.google.com/p/bulk-loader
0 stars 0 forks source link

Error: BulkLoader with name'mainXMLoader' has already been created. #46

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. create 2 swfs with a bulkloader that will load an xml doc
2. name the bulkloader in each swf the same id
3. create a third swf that will use bulkloader to load the first two swfs
4. test the clip

What is the expected output? What do you see instead?

I am creating a 2 - 3 level carousel stack. And I have already built a
carousel swf, so I expect to be able to load the same swf with different
images.

I can load a single instance fine, but I can not load two, and I get the
following output:

All loaders
     [BulkLoader] name:carLoader, itemsTotal: 2, itemsLoaded: 0
     [BulkLoader] name:mainXMLoader, itemsTotal: 1, itemsLoaded: 0
     [BulkLoader] name:picLoader, itemsTotal: 0, itemsLoaded: 0
     [BulkLoader] name:shellLoader, itemsTotal: 0, itemsLoaded: 0
===========
Error: BulkLoader with name'mainXMLoader' has already been created.
    at br.com.stimuli.loading::BulkLoader()
    at mixandmatch_bottoms_fla::MainTimeline/frame1()

What version of the product are you using? On what operating system?

bulkloader_rev_196
Mac OSX
Flash CS3
AS3

Please provide any additional information below.

Is there a way to isolate the swfs so that the loaders carryout, or can a
local connection be worked in to take a single swf and pass a variable to
determine the content?

Original issue reported on code.google.com by bousque...@gmail.com on 31 Jul 2008 at 2:49

GoogleCodeExporter commented 8 years ago 
I just used Loader () to bring in a "tops" swf and a "bottoms" swf, both using a
bulkloader named "mainXMLLoader" and they loaded in working order.

The issue only arrises if I use BulkLoader to load the two swfs.

Original comment by bousque...@gmail.com on 31 Jul 2008 at 3:09

GoogleCodeExporter commented 8 years ago 
Hi Busquetcm.

Actually, this is a feature.
Since BulkLoader allows you to do something like 
BulkLoader.getLoader("mainLoader"); from anywhere, it then 
follows that BulkLoader instances must have unique names (at least across the 
same application domain).

The solution for this is to use different names.

In case you are generating BulkLoaders programatically, you can use the 
BulkLoader. 
createUniqueNamedLoader() to generate BulkLoader instances that are guaranteed 
not to cause name clashes.

Cheers
Arthur Debert

Original comment by debert on 5 Aug 2008 at 4:11