dynapi-dev

Re: [Dynapi-Dev] (no subject)

[Jordi M. <jmi...@or...>]

Yeah but we have three subscribers @arista.es ( I'm the admin now, fear 
me !!! ) and I don't know which one is bouncing. I'll send some test 
messages and see which one bounces back.

Dougal Campbell wrote:

>I don't speak Spanish, but best I can tell, this is a "this email
>address is invalid" message. Who here has authority to remove this
>address from the mailing list?
>
>On Mon, 1 Oct 2001, Pascal Bestebroer wrote:
>
>>OEH! I know! try english!
>>
>>Pascal Bestebroer
>>pa...@dy...
>>http://www.dynamic-core.net
>>
>>>-----Oorspronkelijk bericht-----
>>>Van: dyn...@li...
>>>[mailto:dyn...@li...]Namens ar...@ar...
>>>Verzonden: maandag 1 oktober 2001 21:29
>>>Aan: dyn...@li...
>>>Onderwerp: [Dynapi-Dev] (no subject)
>>>
>>>
>>>La dirección de correo a la que ha escrito no existe o es incorrecta,
>>>por favor compruebe que la dirección es correcta, y si el
>>>problema persiste
>>>pongase en contacto con nosotros en el e-mail: ar...@ar...
>>>
>>>
>>>_______________________________________________
>>>Dynapi-Dev mailing list
>>>Dyn...@li...
>>>https://lists.sourceforge.net/lists/listinfo/dynapi-dev
>>>
>>
>>_______________________________________________
>>Dynapi-Dev mailing list
>>Dyn...@li...
>>https://lists.sourceforge.net/lists/listinfo/dynapi-dev
>>
>

Re: [Dynapi-Dev] (no subject)

[Raides J. <ra...@te...>]

Dougal Campbell wrote:
> 
> I don't speak Spanish, but best I can tell, this is a "this email
> address is invalid" message. Who here has authority to remove this
> address from the mailing list?
> 
> On Mon, 1 Oct 2001, Pascal Bestebroer wrote:
> 
> > OEH! I know! try english!
> >
> > Pascal Bestebroer
> > pa...@dy...
> > http://www.dynamic-core.net
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens ar...@ar...
> > > Verzonden: maandag 1 oktober 2001 21:29
> > > Aan: dyn...@li...
> > > Onderwerp: [Dynapi-Dev] (no subject)
> > >
> > >
> > > La dirección de correo a la que ha escrito no existe o es incorrecta,
> > > por favor compruebe que la dirección es correcta, y si el
> > > problema persiste
> > > pongase en contacto con nosotros en el e-mail: ar...@ar...

 (snip)

	Easy shot this one!

	This just means that someone with an xx...@ar... address has
subscribed to this list and has been taken offline from the mail server
withouth doing proper unsubscription. So if Jordi is now the
administrator of the list, he'll the one in charge of browsing through
the complete subscriber list and delete (after trying to contact them
first) all non-working xxx...@ar... addresses and that's all!

	Regards,

	Raides J.

Re: [Dynapi-Dev] (no subject)

[<ro...@si...>]

You are very right!!

this mail address doesnt exist anymore, can somebody remove it please??

----- Original Message -----
From: "Dougal Campbell" <do...@gu...>
To: <dyn...@li...>
Sent: Monday, October 01, 2001 1:46 PM
Subject: RE: [Dynapi-Dev] (no subject)


I don't speak Spanish, but best I can tell, this is a "this email
address is invalid" message. Who here has authority to remove this
address from the mailing list?

On Mon, 1 Oct 2001, Pascal Bestebroer wrote:

> OEH! I know! try english!
>
> Pascal Bestebroer
> pa...@dy...
> http://www.dynamic-core.net
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens ar...@ar...
> > Verzonden: maandag 1 oktober 2001 21:29
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] (no subject)
> >
> >
> > La dirección de correo a la que ha escrito no existe o es incorrecta,
> > por favor compruebe que la dirección es correcta, y si el
> > problema persiste
> > pongase en contacto con nosotros en el e-mail: ar...@ar...
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > https://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

--
Ernest MacDougal Campbell III, MCP+I, MCSE <do...@gu...>
http://dougal.gunters.org/        http://spam.gunters.org/
Lumber Cartel Unit #1654 (tinlc): http://come.to/the.lumber.cartel/
This message is guaranteed to be 100% eror frea!


_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapi-dev

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

RE: [Dynapi-Dev] (no subject)

[FERNANDO N. <ma...@fe...>]

The message translates to:
"The mail address you have written to doesn't exist or is incorrect,
please check if the address is correct, and if the problem persists
get in touch with us thru the e-mail: ar...@ar...
"

Greetings from Portugal,
Fernando Nunes

-----Mensagem original-----
De: dyn...@li...
[mailto:dyn...@li...]Em nome de
ar...@ar...
Enviada: Quinta-feira, 4 de Outubro de 2001 20:06
Para: dyn...@li...
Assunto: [Dynapi-Dev] (no subject)


La direcci=F3n de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la direcci=F3n es correcta, y si el problema pers=
iste
pongase en contacto con nosotros en el e-mail: ar...@ar...


_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] (no subject)

[Jordi M. <jmi...@or...>]

I think I've identified the adress in arista.es that was bouncing back. 
I've disabled that adress. Hope this removes those annoying messages

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

[Dynapi-Dev] (no subject)

[<ar...@ar...>]

La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: ar...@ar...

[Dynapi-Dev] (no subject)

[Laszlo T. <las...@po...>]

Could one of the admins look at the list settings on sourceforge, and see if
there is a way to set the <From> line to the list's address instead of the
person who is sending the email. This will allow us to reply to the list
instead of the person.

Who knows how many good replies the group misses, because the replies only
get sent to the originator.

NanoFace =:^)

Re: [Dynapi-Dev] (no subject)

[Robert R. <rrr...@ya...>]

Sourceforge no longer allows this option.  Check the sf.net archives
for the news item relating to this.

Robert

On 11/14/2001, Laszlo Teglas wrote:
> Could one of the admins look at the list settings on sourceforge, and see if
> there is a way to set the <From> line to the list's address instead of the
> person who is sending the email. This will allow us to reply to the list
> instead of the person.

> Who knows how many good replies the group misses, because the replies only
> get sent to the originator.

> NanoFace =:^)


> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

[Dynapi-Dev] (no subject)

[Quang N. <ye...@ho...>]

I was playing around the file
dynapi-2.5.6\dynapi\examples\dynapi.ext.inline.htm, when I realized that all 
the layers get messup when I resized the browser Netscape® Communicator 
4.76. Not only the two original layers are gone, but 3 layers(one is red 
even through I have never defined red color in the code) appear. After 
checking on the documentation, the following code should have fix this bug, 
but nothing new happen:
DynAPI.onResize = DynAPI.onLoad = function()


It seems this bug is within the following statement: 
this.document.getAll()['layer1'])

Does anyone have an idea?

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

Re: [Dynapi-Dev] (no subject)

[Richard B. <ric...@sk...>]

If I understand you right, you're talking about the NS4 resize bug. (FAQ)
We have a "fix" for this browser bug, but it doesn't as yet work for
Dynimages, or inline layers, and on large pages it fails too.
Basically this is a tricky issue that is hard to solve.

Richard.

----- Original Message -----
From: "Quang Nguyen" <ye...@ho...>
To: <Dyn...@li...>
Sent: Wednesday, November 21, 2001 12:31 AM
Subject: [Dynapi-Dev] (no subject)


> I was playing around the file
> dynapi-2.5.6\dynapi\examples\dynapi.ext.inline.htm, when I realized tha=
t
all
> the layers get messup when I resized the browser Netscape=AE Communicat=
or
> 4.76. Not only the two original layers are gone, but 3 layers(one is re=
d
> even through I have never defined red color in the code) appear. After
> checking on the documentation, the following code should have fix this
bug,
> but nothing new happen:
> DynAPI.onResize =3D DynAPI.onLoad =3D function()
>
>
> It seems this bug is within the following statement:
> this.document.getAll()['layer1'])
>
> Does anyone have an idea?
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.=
asp
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>

Re: [Dynapi-Dev] (no subject)

[Doug M. <do...@cr...>]

Actually it does work on inline layers.
You just have to call findLayers every time you dynamically add a layer in
HTML (via setHTML() ect.)
I have a mod that will keep it from re-adding layers it had already found.
I'll post it when I get to the office tomorrow.
----- Original Message -----
From: "Richard Bennett" <ric...@sk...>
To: "Quang Nguyen" <ye...@ho...>; <Dyn...@li...>
Sent: Tuesday, November 20, 2001 7:37 PM
Subject: Re: [Dynapi-Dev] (no subject)


If I understand you right, you're talking about the NS4 resize bug. (FAQ)
We have a "fix" for this browser bug, but it doesn't as yet work for
Dynimages, or inline layers, and on large pages it fails too.
Basically this is a tricky issue that is hard to solve.

Richard.

----- Original Message -----
From: "Quang Nguyen" <ye...@ho...>
To: <Dyn...@li...>
Sent: Wednesday, November 21, 2001 12:31 AM
Subject: [Dynapi-Dev] (no subject)


> I was playing around the file
> dynapi-2.5.6\dynapi\examples\dynapi.ext.inline.htm, when I realized that
all
> the layers get messup when I resized the browser Netscape® Communicator
> 4.76. Not only the two original layers are gone, but 3 layers(one is red
> even through I have never defined red color in the code) appear. After
> checking on the documentation, the following code should have fix this
bug,
> but nothing new happen:
> DynAPI.onResize = DynAPI.onLoad = function()
>
>
> It seems this bug is within the following statement:
> this.document.getAll()['layer1'])
>
> Does anyone have an idea?
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>


_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] (no subject)

[Doug M. <do...@cr...>]

And here it is (for the second time)
I've renamed the extension as the sourceforge mail servers are now bouncing
messages with attached .js files//
just rename inline.j_ to inline.js

----- Original Message -----
From: "Doug Melvin" <do...@cr...>
To: "Richard Bennett" <ric...@sk...>; "Quang Nguyen"
<ye...@ho...>; <Dyn...@li...>
Sent: Tuesday, November 20, 2001 11:37 PM
Subject: Re: [Dynapi-Dev] (no subject)


> Actually it does work on inline layers.
> You just have to call findLayers every time you dynamically add a layer in
> HTML (via setHTML() ect.)
> I have a mod that will keep it from re-adding layers it had already found.
> I'll post it when I get to the office tomorrow.
> ----- Original Message -----
> From: "Richard Bennett" <ric...@sk...>
> To: "Quang Nguyen" <ye...@ho...>;
<Dyn...@li...>
> Sent: Tuesday, November 20, 2001 7:37 PM
> Subject: Re: [Dynapi-Dev] (no subject)
>
>
> If I understand you right, you're talking about the NS4 resize bug. (FAQ)
> We have a "fix" for this browser bug, but it doesn't as yet work for
> Dynimages, or inline layers, and on large pages it fails too.
> Basically this is a tricky issue that is hard to solve.
>
> Richard.
>
> ----- Original Message -----
> From: "Quang Nguyen" <ye...@ho...>
> To: <Dyn...@li...>
> Sent: Wednesday, November 21, 2001 12:31 AM
> Subject: [Dynapi-Dev] (no subject)
>
>
> > I was playing around the file
> > dynapi-2.5.6\dynapi\examples\dynapi.ext.inline.htm, when I realized that
> all
> > the layers get messup when I resized the browser Netscape® Communicator
> > 4.76. Not only the two original layers are gone, but 3 layers(one is red
> > even through I have never defined red color in the code) appear. After
> > checking on the documentation, the following code should have fix this
> bug,
> > but nothing new happen:
> > DynAPI.onResize = DynAPI.onLoad = function()
> >
> >
> > It seems this bug is within the following statement:
> > this.document.getAll()['layer1'])
> >
> > Does anyone have an idea?
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at
http://explorer.msn.com/intl.asp
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://www.mail-archive.com/dyn...@li.../
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] (no subject)

[Raymond I. <xw...@ya...>]

Hello,

This looks good. I think it should replace the current
inline.js in the DynAPI Core

Can that be done?

--
Raymond

--- Doug Melvin <do...@cr...> wrote:
> And here it is (for the second time)
> I've renamed the extension as the sourceforge mail
> servers are now bouncing
> messages with attached .js files//
> just rename inline.j_ to inline.js
> 
> ----- Original Message -----
> From: "Doug Melvin" <do...@cr...>
> To: "Richard Bennett" <ric...@sk...>;
> "Quang Nguyen"
> <ye...@ho...>;
> <Dyn...@li...>
> Sent: Tuesday, November 20, 2001 11:37 PM
> Subject: Re: [Dynapi-Dev] (no subject)
> 
> 
> > Actually it does work on inline layers.
> > You just have to call findLayers every time you
> dynamically add a layer in
> > HTML (via setHTML() ect.)
> > I have a mod that will keep it from re-adding
> layers it had already found.
> > I'll post it when I get to the office tomorrow.
> > ----- Original Message -----
> > From: "Richard Bennett"
> <ric...@sk...>
> > To: "Quang Nguyen" <ye...@ho...>;
> <Dyn...@li...>
> > Sent: Tuesday, November 20, 2001 7:37 PM
> > Subject: Re: [Dynapi-Dev] (no subject)
> >
> >
> > If I understand you right, you're talking about
> the NS4 resize bug. (FAQ)
> > We have a "fix" for this browser bug, but it
> doesn't as yet work for
> > Dynimages, or inline layers, and on large pages it
> fails too.
> > Basically this is a tricky issue that is hard to
> solve.
> >
> > Richard.
> >
> > ----- Original Message -----
> > From: "Quang Nguyen" <ye...@ho...>
> > To: <Dyn...@li...>
> > Sent: Wednesday, November 21, 2001 12:31 AM
> > Subject: [Dynapi-Dev] (no subject)
> >
> >
> > > I was playing around the file
> > >
> dynapi-2.5.6\dynapi\examples\dynapi.ext.inline.htm,
> when I realized that
> > all
> > > the layers get messup when I resized the browser
> Netscape® Communicator
> > > 4.76. Not only the two original layers are gone,
> but 3 layers(one is red
> > > even through I have never defined red color in
> the code) appear. After
> > > checking on the documentation, the following
> code should have fix this
> > bug,
> > > but nothing new happen:
> > > DynAPI.onResize = DynAPI.onLoad = function()
> > >
> > >
> > > It seems this bug is within the following
> statement:
> > > this.document.getAll()['layer1'])
> > >
> > > Does anyone have an idea?
> > >
> > >
>
_________________________________________________________________
> > > Get your FREE download of MSN Explorer at
> http://explorer.msn.com/intl.asp
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > >
>
http://www.mail-archive.com/dyn...@li.../
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
>
http://www.mail-archive.com/dyn...@li.../
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
>
http://www.mail-archive.com/dyn...@li.../
> 

> ATTACHMENT part 2 application/octet-stream
name=inline.j_



__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

[Dynapi-Dev] (no subject)

[Doug M. <do...@cr...>]

heloooo... is this thing on?

Re: [Dynapi-Dev] (no subject)

[Robert R. <rai...@us...>]

If we choose to set the children array to null, then maybe we should
have an function hasChildren() that returns a boolean.

Later,
Robert <rai...@us...>

> So I've posted a patch for DynLayer and DynDocument that assigns the
> this.children array only when you use addChild.  DynLayer-based widgets
> won't have a children array until you add at least one child.
> 
> I also made changes to removeChild, removeAllChildren, etc. that check for
> the existence of the child array before proceeding.
> 
> This should ensure that the children array is a unique object for each
> widget, and not the common one in the Widget prototype.  Then you can safely
> use WidgetX to simulate inheritance without the shared-properties problem.
> 
> The only consideration is if you build a widget that manipulates the
> children array, you should test it it exists first (it's initially set to
> null until you use addChild).
> 
> I've only tested it on a few IBS and GUI widgets, but it seems to work
> across the board.  I've posted the patch for review.
> 
> scottandrew

Re: [Dynapi-Dev] (no subject)

[Robert R. <rai...@us...>]

There's also a bit of inconsistency with making the children array
null.   Because once you remove all the children, the array is not
null, but has a length of 0.  So, in your widget, you will have to
check for a null array and a array of length 0.  I don't understand
why the array can't be initialized to an empty array.


Later,
Robert <rai...@us...>

> I think I've found a fix for the problem with children arrays being shared
> between widgets made with the widgetX  model.
> 
> The problem:
> 
> Widget.prototype = new DynLayer()
> 
> When this is done, the properties of the base DynLayer are *shared* with
> every Widget made with the constructor.
> 
> Most of these shared properties are reassigned to unique ones when
> createElement is called on the Widget.  However, the children array is not,
> and it gives the effect that all Widgets share the same children array.
> 
> So I've posted a patch for DynLayer and DynDocument that assigns the
> this.children array only when you use addChild.  DynLayer-based widgets
> won't have a children array until you add at least one child.
> 
> I also made changes to removeChild, removeAllChildren, etc. that check for
> the existence of the child array before proceeding.
> 
> This should ensure that the children array is a unique object for each
> widget, and not the common one in the Widget prototype.  Then you can safely
> use WidgetX to simulate inheritance without the shared-properties problem.
> 
> The only consideration is if you build a widget that manipulates the
> children array, you should test it it exists first (it's initially set to
> null until you use addChild).
> 
> I've only tested it on a few IBS and GUI widgets, but it seems to work
> across the board.  I've posted the patch for review.
> 
> scottandrew
> 
> 
> 
> 
> 
> 
> ------
> Scott Andrew LePera
> DHTML / Scripting / CGI and other neat stuff
> sc...@sc...
> http://www.scottandrew.com

RE: [Dynapi-Dev] (no subject)

[Pascal B. <pa...@dy...>]

I think there's another way of solving this..  By slightly changing the
way widgets are created (still using the same inheriting methods)

here's an example:


function CoreButton(x,y,w,h,caption,flat) {
	this.DynLayer = DynLayer
	this.DynLayer()

	this.id = "CoreButton"+(CoreButton.Count++)

	this.moveTo(x||0,y||0)
	this.setSize(w||128,h||36)

	this.caption=caption||''

	this.lcaption=new DynLayer(null,2,2)
	this.levents=new DynLayer(null,0,0)

	this.lcaption.setVisible(true)
	this.levents.setVisible(true)

	this.setFlat(flat||false)
	this.setVisible(true)

	this.style=new CoreStyle()

	this.children=[]

	return this
}
CoreButton.Count=0
CoreButton.prototype = new DynLayer()

The first lines in the constructor show the main change, I actually think
somebody
else had already mentioned this a while back but I didn't look at it then :(

This is actually the way Netscape is talking about creating objects on the
tutorial sites.

I think this solves the problem with the children array, so that no changes
are needed to
the dynlayer constructor. The widget will still be an "enhancded" dynlayer.

I've also been working on benchmark / test code and I'll try to post it so
that people
can look at it and run some tests in other browsers.

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

Re: [Dynapi-Dev] (no subject)

[Robert R. <rai...@us...>]

Hi,

I beleive there is a bug in the patch:

DynDocument.prototype.recreateAll=function() {
        this.setBgColor(this.bgColor)
        this.setFgColor(this.fgColor)      
        if (this.children) return     //<- should be (!this.children)
        for (var i in this.children) { 
                if (this.children[i].created) {  
                        if (this.children[i].elm) this.children[i].elm=null
                        this.children[i].deleteElement()
                        this.children[i].createElement()
                }
        }
}

Also, I think that you need to use the hasChildren method instead,
because if you add a child and then remove it, the .children will be
true, but have a length of zero.  So, I would sugget using the
hasChildren check instead.

Later,
Robert <rai...@us...>


> I think I've found a fix for the problem with children arrays being shared
> between widgets made with the widgetX  model.
> 
> The problem:
> 
> Widget.prototype = new DynLayer()
> 
> When this is done, the properties of the base DynLayer are *shared* with
> every Widget made with the constructor.
> 
> Most of these shared properties are reassigned to unique ones when
> createElement is called on the Widget.  However, the children array is not,
> and it gives the effect that all Widgets share the same children array.
> 
> So I've posted a patch for DynLayer and DynDocument that assigns the
> this.children array only when you use addChild.  DynLayer-based widgets
> won't have a children array until you add at least one child.
> 
> I also made changes to removeChild, removeAllChildren, etc. that check for
> the existence of the child array before proceeding.
> 
> This should ensure that the children array is a unique object for each
> widget, and not the common one in the Widget prototype.  Then you can safely
> use WidgetX to simulate inheritance without the shared-properties problem.
> 
> The only consideration is if you build a widget that manipulates the
> children array, you should test it it exists first (it's initially set to
> null until you use addChild).
> 
> I've only tested it on a few IBS and GUI widgets, but it seems to work
> across the board.  I've posted the patch for review.
> 
> scottandrew
> 
> 
> 
> 
> 
> 
> ------
> Scott Andrew LePera
> DHTML / Scripting / CGI and other neat stuff
> sc...@sc...
> http://www.scottandrew.com
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev