I just want to clear up that the problem with the delete has nothing
to do with recycled layers or resizing in NS.
After looking a bit further, it appears the current recreation on
resize is only recreating top level layers. This is why it is not
working. Hopefully, I'll have a complete solution soon.
--
Robert Rainwater
On 6/18/2001, 4:27:22 PM EST, Doug wrote about "[Dynapi-Dev] Attention...":
> I think that what everyone is forgetting is that the current DynAPI is a
> Completely re-worked early version 2.
> (remember DynAPI X?)
> SO.. Resizing does NOT work in NS.
> Period.
> So let's stop arguing over what worked when and concentrate on the the fact
> that RIGT NOW we have a problem.
> ----- Original Message -----
> From: "Robert Rainwater" <[EMAIL PROTECTED]>
> To: "D. Joannou" <[EMAIL PROTECTED]>
> Sent: Sunday, June 17, 2001 8:25 PM
> Subject: Re[9]: [Dynapi-Dev] Attention...
>>
>>
>>
>>
>> On 6/17/2001, 11:16:50 PM EST, D. wrote about "[Dynapi-Dev] Attention...":
>>
>> >> It is being handled by the DynAPI. If it wasn't then it would have
>> >> never worked in NS.
>>
>> > There must be some sort of misunderstanding here.
>> > I am using v.2.53.
>> > If it did work, then should I be getting a javascript error???
>>
>> > Line number: 77.
>>
>> > Message: c is permanent.
>>
>> > I don't see how this is considered as "working"!
>>
>> > Richard Bennett said I may be missing a line from the latest CVS.
>> > I added the line and still the same error. Anyway the workaround
>> > I mentioned in previous correspondence works for me for the time being.
>>
>> >>If you look at the specificRemove in dynlayer.js
>> >> you will see how it works. The visibility is hidden and it is stored
>> >> in a recycled array. It doesn't require any work on your part to use
>> >> recycled arrays.
>> >>
>> >> Robert Rainwater
>>
>> > Let's get it working without generating errors first, and then we can
> talk
>> > about the recycling bit, wouldn't you agree?
>>
>> Recycling has nothing to do with the error you are getting. Recycling
>> has been in the DynAPI since a few months after DynAPI 2 was created.
>> The problem with removal is a problem with the DynAPIObject not
>> recycled layers in NS. The workaround posted with stop the errors but
>> will cause some memory leaks in IE.
>>
>>
>>
>>
>> --
>> Robert Rainwater
>>
>>
>> _______________________________________________
>> Dynapi-Dev mailing list
>> [EMAIL PROTECTED]
>> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
