There is some other strange stuff going on though, I'm using IE7 which might or might not
have something to do with it. It seems like even though we are using the DeclareEvent mechanism,
there is some error happening when sendEvent is called in some situations which run fine in Firefox.
Also some errors happen in similar kinds of function dispatch situations, like in this method
LzNode.prototype.__LZresolveReferences = function (){
var rdict = this.__LZresolveDict;
this.__LZresolveDict = null;
for ( var r in rdict ){
this[ this.__LZdelayedSetters[ r ] ] ( rdict[ r ] );
}
}
IE gets errors as if the objects it is calling are not functions, or else it is actually
complaining about the number of arguments not matching or something. I'm trying to pin it down.
On 6/13/06, P T Withington <
[EMAIL PROTECTED]> wrote:
On 2006-06-13, at 19:33 EDT, Henry Minsky wrote:
> DEBUG: Can't name event <_javascript_:top.$modules.lz.Debug.displayObj
> (0)>
>
> In IE, I get that warning --- according to Max
> http://msdn.microsoft.com/library/default.asp?url="">
> jscript7/html/jsreserved.asp'event'
> is indeed a reserved word.
> But why are we trying to assign to it? Guess it's enumerated
> someplace by
> the debugger?
That should be innocuous. The debugger is just looping through the
global objects and trying to give them pretty names. Is is causing a
problem? If so, I can change the way this is handled...
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
_______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
