I tried this too, but AFAIK native elements don't have the prototype
property, so it fails.
You can - in some instances - expand on a native element's properties, but
only for a single instance.
The solution is of course to use a "holder" object, that creates the image
(or whatever) and then takes over its properties as if they were it's own,
like Dynlayer.
Cheers,
Richard.
----- Original Message -----
From: "martin ström" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 17, 2001 6:17 PM
Subject: RE: [Dynapi-Dev] dynimage
> i think the loader-part of dynimage is great, but i have not used
> the DynImage-object ever..
>
> btw, is it possible to inherit from a native js-object, something like
>
> function MyImage() {
> this.Image = Image;
> this.Image();
> }
> MyImage.prototype = new Image();
>
> didn't inherit correctly for me..
> any ideas?
>
> /martin
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]] On Behalf Of
> > Jordi Ministral
> > Sent: den 17 oktober 2001 17:52
> > To: DynAPI-Dev
> > Subject: [Dynapi-Dev] dynimage
> >
> >
> > Someone please convince me it is worth using. Honestly I think that's
> > forcing things too much: an object that encapsulates the already
> > existing Image object...
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > [EMAIL PROTECTED]
> > http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
