Hello again :)
I've tested the 8-3-01 snapshot example: dynapi.gui.scrollpane.html in
NS4.08 & W98SE and when you resize the screen, as it's NS4, it tries to
recreate all the objects just deleting them and creating again. The
problem is that it doesn't work, because the scrollpanel is just delet
I think that it only changes the cursor, but doesn't create a layer.
Actually, it works fine in IE !
> -Mensaje original-
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]En nombre de Doug Melvin
> Enviado el: sábado, 10 de marzo de 2001 0:53
> Para: [EMAIL PROTECTED]
> Asunto: Re: [Dy
I think the forced CollectGarbage(); makes a big difference. I had the
same problem and calling this worked wonders. I remember reading that if a
page uses a newwin=window.open that you've created an explicit reference to
the new window and the 10-12 second lag (with layer intensive pages) is
p
Darryl,
A little feedback from the trails of site optimization. For your title page
you should build a "static park frame" in your flash movie and when a
secondary window is launched send the title page window to "park".
Even those little animated lines in flash eat about 50% of a 200-300 mhz P
Thanks Robert for the reply.
On the two 'guilty' links I was loading html pages with plenty of DynAPI2
script. I assume that it is a memory problem with IE. It gets itself tied up
with the DynAPI in the opened windows and when they're closed again it takes
those several seconds to free up the mem
I tried and didn't have that problem with adding some simple dynlayers
to the window. What exactly are you loading in the windows?
--
Robert Rainwater
On 3/10/2001, 5:34:08 AM EST, Darryl wrote about "[Dynapi-Help] window.open and IE":
> Hello All,
> I have a home page with several links (
