PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, November 19, 2001 7:59 PM
Subject: Re: [Dynapi-Dev] Question about DynAPIObject
> Sorry for my last messy post. Here is a much better version:
>
>
> I tried the following code, but the layer 'myLayer' didn't get hidden.
rs.mylayer);
d.setVisible(false) //This doesn't work
Original Message Follows
From: Dan Steinman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Question about DynAPIObject
Date: Sat, 10 Nov 2001 00:37:26 -0500
The reason for DynAPI to create the laye
.mylayer); //
assignElement is re-introduced in 2.6
d.setVisible(false);
</script>
Original Message Follows
From: Dan Steinman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Question about DynAPIObject
Date: Sat, 10 Nov 2001 00:37:26 -0500
The reason
The reason for DynAPI to create the layer/div is to make it easier. There's nothing
stopping you from creating your layers manually, and then attaching them to a DynLayer
afterwords like so:
d = new DynLayer();
d.setID('mylayer');
d.assignElement(is.ie?document.all.mylayer:document.layers.my
Because with the current system, dynlayers can only be created after
the page has loaded. And since the dynapi captures the onload event,
you must use DynAPI.onLoad to create objects after the page has
loaded. Apparently, the next version will support creating of
dynlayers before the page loads
, and only add them to the document when you need
them.
Richard
- Original Message -
From: "Quang Nguyen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 10, 2001 12:32 AM
Subject: [Dynapi-Dev] Question about DynAPIObject
> I guess we create a
I guess we create a DynAPI object to make sure the Dynapi.js and any library
needed have been loaded.
However, what are the technical reason why we need DynAPI to create a layer,
like the following:
...
DynAPI.onLoad = function()
{
myLayer = new DynLayer()
myLayer.setSize(100,1
