> Then test it.
> I'm sure we don't need to hold your hand.
I asked on this list to learn the facts the core developers are
basing their opinions on. Sure I can do everything on my own, but - as
I see it - we all do profit if we exchange our experiences and try to
improve our understanding of the
clearing up the browser memory problems (although Jordi already mentioned it
I think)
if you have javascript objects/variables referencing DOM elements (html
divs, images, mouseevents etc) you need to make sure those are deleted
(de-attached from the html elements) or the html elements will keep
I dropped my coffee cup...
But it's always good to hear a little Pascal in the morning.
DS
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Pascal
Bestebroer
Sent: Tuesday, June 19, 2001 6:47 AM
To: [EMAIL PROTECTED]
Subject: RE: Re[13]: [Dynapi-Dev] Att
There's a memory test I used before to test Eytans tcanvas:
http://www.dynapi.f2s.com/dynapi/tcanvas/stress.dynlayer.create%20wtime200.h
tm
It creates 200 dynlayers, and times this.
When we had the memory leak (up till v 2.51) this time would keep increasing
after refreshing IE5, and running it a
> clearing up the browser memory problems (although Jordi already mentioned it
> I think)
Thank you for your effort.
> so every DynLayer has a reference to atleast an HTMLDIVElement.. that has to
> be removed by setting the variables/objects to null
>
> so:
>
> DynLayer.elm=null
>
> would rem
Patches item #434363, was updated on 2001-06-18 23:13
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=305757&aid=434363&group_id=5757
Category: DynAPI 2 Widget
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Pemberton (mpember)
Assigned t
> I don't think changing it to c=null will influence anything in a bad way.
> Unless someone knows different I think we can change this, and close this
> bug.
Jordi has already done so yesterday :-)
Stephan
___
Dynapi-Dev mailing list
[EMAIL PROTECTE
> As far as I understand, all references to HTMLDIVElements are removed
> in Dynlayer.specificRemove.
>
> What I'm still questioning is that there's a difference in memory
> handling between "delete obj" and "obj = null" and that one has to
> delete or assign null to the argument of DynObject.dele
> Now that things have proven stable and looking at those lines of code doesn't
> revive any traumas, we can see if some can be removed. Probably the
> Methods.delete is not needed as well as other deletion code, as long as the
> specificRemove is called when something is removed, something that i
> > O boy do I remember the good ol' days when nothin' worked at
> all, those were
> > tough times, you know. Difficult times, you could feel the presure, the
> > complains of memory leaks... aaahh, the pressure, the anger,
> the frustration...
>
> Maybe you should write a new API ;-)
now THE
Sorry to jump in after this issue has been debated to a halt, but I have been busy.
About the "delete" operator...
Microsoft's documentation:
http://msdn.microsoft.com/scripting/default.htm?/scripting/jscript/doc/jsoprDelete.htm
Netscape's documentation:
http://developer.netscape.com/docs/manua
Don't give him any ideas:)
--
Robert Rainwater
On 6/19/2001, 12:35:13 PM EST, Pascal wrote about "[Dynapi-Dev] Attention...":
>> > O boy do I remember the good ol' days when nothin' worked at
>> all, those were
>> > tough times, you know. Difficult times, you could feel the presure, the
>>
I have a pretty simple website that I built with dynapi 2.53. When I
tested it with all my browsers running off the local hard drive,
everything worked fine. When I uploaded to my server howerever, only
Internet Explorer 5.0 behaves as expected. Netscape 4.75 (Linux) &
Netscape 4.06 (Window98)
Please check out
http://dynapi.sourceforge.net/cgi-bin/snapshot.pl?file=current . It
includes the latest resize fix for Netscape. Hopefully it should fix
the previous problems.
--
Robert Rainwater
_
Do You Yahoo!?
Get your free @yahoo.
Before the next release we need to fix the loadPanel resizing. In IE
atleast, when you resize a loadPanel with a url already loaded it
disappears. The problem appears to be the reload() method. It clears out
the contents when the dynlayer is resized. Why is it doing this?
Simply removing the meth
I noticed that the updated code still uses the first element of the
recycled array instead of the last.
I suggest that this be changed to remove the overhead of using the
removeFromArray method.
Also, if you are going off what I emailed you, you missed a vital line of
code. The recreate method
16 matches
Mail list logo
