Michael Pemberton wrote:this is NOT the case.> I think we need to look more closely at how the loadpanel is coded.
> - this is the only object / widget that uses the onload event. as such it
> should be placed here instead of in the dynlayer.I'm not sure what you mean? LoadPanel invokes a load event. Whether it
is captured or not is up to the developer.
DynLayer.js:
55 this.elm.captureEvents(Event.LOAD);
56 this.elm. {};
LoadPanel.js
146 lyr.
147 lpanel.loadElement.
As show above, the onload event is being sed by the loadpanel.
this is the only widget that uses it. As such, I would suggest moving
it from the dynlayer.js to loadpanel.js
in that case, why don't we stop the actual events instead of stopping the capture of them. It should be possible to force them all to return false instead of actually not handling them.
> - mouse events are released by this widget when it loads a file. WHY?this is only done for netscape 4, the code has been in there for ages,
but the reason seems to be to stop users from clicking on anything while
something is loading, because clicking on something (like a link) kills
the load. i've tried taking that out, but things work better with it
left in.
cheers,cameron.
> Cameron Hart wrote:
>
>
>>>* dynapi.gui.loadpanel.html
>>>
>>> If you select "use IFrame" after loading a file, an error is caused
>>>- exception occurred line 185
>>>
>>This might be a feature rather than a bug :-) I think perhaps the
>>developer should not be able to change the load method after having used
>>the loadpanel already (i mean why would one want to?). the load method
>>should be set before the first call to setURL. perhaps we should change
>>it so calling useIFrame after setURL is called it does nothing.
>>
>>
>>>* dynapi.gui.loadpanel.html
>>>
>>> After clicking on "use ILayer" loading causes error.
>>>
>>i asked a question about this on dynapi-help a while ago. does anyone
>>actually use the iLayer? I tried it but found it killed events on the
>>layer. I'd suggest we remove it entirely.
>>
>>Good to see some thorough bug testing going on :-)
>>
>>Cameron.
>>
>>_______________________________________________
>>Dynapi-Dev mailing list
>>[EMAIL PROTECTED]
>>http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>>
>
> --
> Michael Pemberton
> [EMAIL PROTECTED]
> ICQ: 12107010
>
>
>
>
> _______________________________________________
> 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
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
