I made a note on the WIKI at http://wiki.openlaszlo.org/DHTML_Laszlo#Developer_Notes_for_Legals
We ought to make a slightly less terse list of gotchas for merging LFC code. Everyone, if you get
screwed on somethng while merging, please add a note to the above list.
On 4/24/06, P T Withington <[EMAIL PROTECTED]> wrote:
This should be inherited.
I would try Debug.write-ing LzDataNode.prototype.onparentnode and
LzDataElement.prototype.onparentnode right before instantiating to
see if they are what you expect.
Um. You're not getting screwed by onparentnode vs. onparentNode?
On 2006-04-24, at 12:04 EDT, Henry Minsky wrote:
>
>
> Okay, there really seems to be a bug with events declared with
> DeclareEvent not getting inherited by
> child classes in the DHTML runtime.
>
> For example, if I have LzDataNode which has this declaration
>
> DeclareEvent(LzDataNode.prototype, 'onparentNode' );
>
> And then LzDataElement is defined as
>
> LzDataElement = makeLFCConstructor(LzDataNode);
>
> but if I instantiate an LzDataElement, using LzFactory.create (),
> it's onparentNode is null instead of an LzDeclaredEvent
>
> So who is responsible for making sure that default properties of
> the superclass are visible in an instance of the subclass?
>
>
> The question I have is how should this be getting inherited, and is
> there something magic in the __construct
> constructor function that I should be calling to make this happen?
> Is it required to call
> this.callInherited( '__construct', arguments.callee)
>
> That doesn't seem to make any difference in the inheritance of the
> onparentNode property ..
>
>
>
>
>
>
>
>
>
>
>
> --
> Henry Minsky
> Software Architect
> [EMAIL PROTECTED]
>
> _______________________________________________
> Laszlo-dev mailing list
> [email protected]
> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
_______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
