[Laszlo-dev] replicator naming bug seems to be due to difference in order that early setters is executed in trunk vs legals
Henry Minsky
henry.minsky at gmail.com
Mon Nov 6 16:30:39 PST 2006
I put a print statement in the early setters handling in applyArgs, and they
execute in a different order in trunk vs legals.
That seems to be the cause of the bug where the replicator gets replaced by
the original view. The list of earlysetters is
var earlySetters ={
name : true ,
id : true ,
$events : true ,
$delegates : true ,
$classrootdepth : true ,
$datapath : true
};
So the question is are there any other subtle bugs due to interactions from
the order these things get executed?
trunk:
early setter name entry [VIEW]
early setter $datapath {attrs: [object Object], name: LzDatapath}
early setter name entry [REPLICATOR]
early setter id «undefined»
legals:
early setter $datapath {attrs: [object Object], name: datapath}
early setter name entry [ REPLICATOR ]
early setter id «undefined»
early setter name entry [ VIEW ]
WARNING: Redefining #outer.entry from «LzReplicationManager#3#2|
ReplicationManager in LzView name: outer id: outer » to «LzView#5#4»
--
Henry Minsky
Software Architect
hminsky at laszlosystems.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.openlaszlo.org/pipermail/laszlo-dev/attachments/20061106/28397387/attachment-0001.html
More information about the Laszlo-dev
mailing list