Okay, I've answered my own question and it has nothing to do with the
frames :)
Sorry for the confusion.
Ben Sargent wrote:
>
> Hello. I have recently been porting my code over to the 'new' Dyn2.0
> way of doing things (as per the changes last month, when we moved from
> core.api.whatever to dynapi.api.whatever). My site uses frames for
> navigation, but due to the nature of the application, I don't want (or
> need) to be able to control frames from other frames (basically, each
> frame is an independent document).
>
> In any case, I'll describe my problem with an example.
>
> page1.html:
> ...
> navToolBar = new ToolBar();
> DynAPI.document.addChild(navToolBar);
> ...
>
> page2.html:
> ...
> navToolBar = new ToolBar();
> DynAPI.document.addChild(navToolBar);
> ...
> (Note that they are the same :)
> Now, in the old 2.0 way of doing things, this seemed to work fine. Now,
> however, when I move to page2.html, I'm told that DynAPI cannot add the
> layers to the document since they already exist there (presumably, since
> they have the same name). I'm assuming that DynAPI.document is pointing
> to the 'parent' document, that is, the one containing all the frames,
> instead of the current document. This is not desirable for my
> application. Can someone suggest a way around this problem, or perhaps
> explain the "new" way of doing this?
>
> Thanks for all you help...
>
> ben
>
> --
> Ben Sargent
> Montage eIntegration Inc.
> www.montage.ca
> GFX: www.infinitespaces.com
> PGP: /pgpkey.txt
> _______________________________________________
> Dynapi-Help mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/dynapi-help
--
Ben Sargent
Montage eIntegration Inc.
www.montage.ca
GFX: www.infinitespaces.com
PGP: /pgpkey.txt
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-help
