dynapi-dev — List related to the current DynAPI Core development

Re: [Dynapi-Dev] Width/Height

[<ni...@pr...>]

this is what I use :
DynLayer.prototype.getContentWidth=function() {
    if (!this.created) return 0
    else {
        if (is.ns4) return this.doc.width
        else if (is.ns5) return parseInt(this.elm.offsetWidth)
		else return parseInt(this.elm.scrollWidth)
    }
}
DynLayer.prototype.getContentHeight=function() {
    if (!this.created) return 0
    else {
        if (is.ns4) return this.doc.height
        else if (is.ns5) return parseInt(this.elm.offsetHeight)
        else return parseInt(this.elm.scrollHeight)
    }
}

> and none seem to work.  This is the source of several problems with the DynAPI in NS 6.

this is true if you try to getContentWidth and Height 
before the layer it's actually shown in the page
coz the browser itself takes time to get the info aboutthe layer ,(sorry but my english sucks)

I've tested in many ways and like i said before in the widget-list the only way is to put a setTimeout for ns6
but that cause other problem when u have a lot of nested layers or complex widget

once the layer it's on the page u can alert(myLayer.getContentWidth()) and it will work

ciao
Y
> 
> -- 
> // Robert Rainwater
> ----------------------
> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
> DynAPI Homepage: http://dynapi.sourceforge.net/
> 
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

[Dynapi-Dev] Width/Height

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

Does anyone know how to get the content width and height of a layer in
NS 6.  I've tried:
this.elm.offsetWidth
this.elm.scrollWidth
this.doc.width

and none seem to work.  This is the source of several problems with
the DynAPI in NS 6.

-- 
// Robert Rainwater
----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

Re[2]: [Dynapi-Dev] ns6 loadpanel update and dynlayer suggestions...

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

That is not really a fix that we should use though.  The reason the
resize doesn't work is that getContentHeight and getContentWidth in NS
6 doesnt work.  If we fix these two methods in the DynLayer, then that
should solve a lot of problems.

-- 
// Robert Rainwater

On 1/22/2001, 10:46:29 AM EST, Cameron wrote about "[Dynapi-Dev] ns6 loadpanel update and dynlayer suggestions...":

> make sure you have to right one, i posted two to the list. the first didn't
> do autoresize, but the second does (kind of).

> it's a work in progress and isn't quite perfect yet.

> at the moment, what ns6 does is load the content into a hidden iframe, and
> then gets the html and set's the innerHTML of the loadpanel to the new HTML.
> If I try and get the size of the loadpanel after I've set the HTML, I can
> only get the size of the visible loadpanel, not the full size of the
> content. What I've done to get around this is get the size of the IFRAME
> before I destroy it. This kind of works, but it's not the real content size
> only an estimate. I don't actually know how to get the correct content
> height/width of a layer in NS6. Does anyone else out there know?

> Cameron.

>> -----Original Message-----
>> From: dyn...@li...
>> [mailto:dyn...@li...]On Behalf Of francesco
>> AGATI
>> Sent: 22 January 2001 15:34
>> To: dyn...@li...
>> Subject: Re: [Dynapi-Dev] ns6 loadpanel update and dynlayer
>> suggestions...
>>
>>
>> on netscape 6 the resize of loadpanel do not function
>>
>>
>> franesco
>>
>> ----- Original Message -----
>> From: "Cameron Hart" <cam...@ya...>
>> To: <dyn...@li...>
>> Sent: Thursday, January 18, 2001 12:33 PM
>> Subject: [Dynapi-Dev] ns6 loadpanel update and dynlayer suggestions...
>>
>>
>> > I've attached an updated loadpanel with Netscape 6
>> > support. I've got the Autoresize working. There are
>> > still some issues though. For one, css styles are not
>> > being applied to whatever's being loaded into
>> > LoadPanel. I have no idea why not. Images aren't
>> > always being loaded, this is also a problem with IE.
>> >
>> > Apart from the NS6 modifications, I've added a 'false'
>> > parameter to all setHTML calls, as I believe LoadPanel
>> > should not invoke load events unless something is
>> > actually loaded.
>> >
>> > I've also got some suggested updates for dynlayer.js.
>> > The first is to setHTML, I've added the noevent check
>> > to the beforeload event invocation. Also, I've moved
>> > this.elm.innerHTML into the else block because this
>> > was setting the HTML twice in NS6, and I don't think
>> > NS4 needs innerHTML to be set?
>> >
>> > 423,424c423
>> > < this.invokeEvent("beforeload");
>> > < this.elm.innerHTML=html;
>> > ---
>> > > if (noevt!=false) this.invokeEvent("beforeload");
>> > 441c440,441
>> > < else

>> > ---
>> > > else {
>> > > this.elm.innerHTML=html;
>> >
>> > I've changed getContentWidth and getContentHeight to
>> > support NS6, although I haven't really tested this bit
>> > properly so I'm not sure that it works:
>> >
>> > 485c485,489
>> > < return this.elm==null? 0 : (is.ns4? this.doc.width
>> > : parseInt(this.elm.scrollWidth));
>> > ---
>> > > if (this.elm==null) return 0;
>> > > else if (is.ns4) return this.doc.width;
>> > > else if (is.ns5) return this.elm.offsetWidth;
>> > > else return parseInt(this.elm.scrollWidth);
>> > > // return this.elm==null? 0 : (is.ns4?
>> > this.doc.width : parseInt(this.elm.scrollWidth));
>> > 488c492,496
>> > < return this.elm==null? 0 : (is.ns4? this.doc.height
>> > : parseInt(this.elm.scrollHeight));
>> > ---
>> > > if (this.elm==null) return 0;
>> > > else if (is.ns4) return this.doc.height;
>> > > else if (is.ns5) return this.elm.offsetHeight;
>> > > else return parseInt(this.elm.scrollHeight);
>> > > // return this.elm==null? 0 : (is.ns4?
>> > this.doc.height : parseInt(this.elm.scrollHeight));
>> >
>> > If there aren't any problems with these changes, I'd
>> > like to add the NS6 enabled LoadPanel to CVS, and the
>> > changes to setHTML.
>> >
>> > Cheers
>> >
>> >
>> > Cameron.
>> >
>> > __________________________________________________
>> > Do You Yahoo!?
>> > Get email at your own domain with Yahoo! Mail.
>> > http://personal.mail.yahoo.com/
>>
>>
>> _______________________________________________
>> Dynapi-Dev mailing list
>> Dyn...@li...
>> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


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


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

RE: [Dynapi-Dev] Oversight (Code generation)

[Raible, M. <MR...@ED...>]

I have misplaced my mail list information on how to unsubscribe from
this list, can someone help me out?
=20
Thanks,
=20
Matt
=20
-----Original Message-----
From: Michael Pemberton [mailto:mp...@ph...]
Sent: Monday, January 22, 2001 8:38 AM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Oversight (Code generation)
=20
I was mucking around with this last night.  the attached file is one
method of doing it.=20
Just include the attached file and call layerName.generateCode() this
should return a copy of the initialisation command for the layer.=20
Pascal wrote:=20
Some secondary values are callable, but certain arrays will give
problems=20
(I'm trying to fix that).=20
I'm not sure if I can retrieve variable names (anyone with an idea on
that=20
one?) But I am planning on creating an extra module like Oversight,
which=20
reads the DynAPI tree of objects (dynapi.document and all child layers)
and=20
regenarets correct code for it.. This would be the first step for
wysiwyg=20
editing.. simple attach dragevent listeners to every layer on screen so
that=20
they can be placed, call the code-generator and you have your wysiwyg
editor=20
Also another idea I'm having is including a better object watcher to=20
Oversight.. like the one found in Delph, Visual basic ,etc.. a window=20
showing all properties and values, make them editable and you have easy=20
access to every object, making the Dump Object obsolete.=20
cya,=20
Pascal Bestebroer (pb...@oi...)=20
Software ontwikkelaar=20
Oberon Informatiesystemen b.v.=20
http://www.oibv.com <http://www.oibv.com> =20
> -----Oorspronkelijk bericht-----=20
> Van: dyn...@li...=20
> [ mailto:dyn...@li...
<mailto:dyn...@li...> ]Namens Richard Bennett=20
> Verzonden: maandag 22 januari 2001 0:42=20
> Aan: dyn...@li...=20
> Onderwerp: Re: [Dynapi-Dev] Oversight=20
>=20
>=20
> Hi,=20
> This was another amazing job, both of you, I'll add it to=20
> every example on=20
> my site with the next release,=20
> and have it called from a link instead of my DynAPIDiagnose.=20
> A few points:=20
>     you probably know dumping the secondary values from the hyperlinks

> doesn't work yet.=20
>     Is it possible to get a clickable list of the objects on=20
> the page by the=20
> name they were defined by, like this:=20
>=20
>     Available objects on this page:=20
>     * MyLayer=20
>             *MyChildLayer=20
>=20
>     * SkinWindow1=20
>             *myPushPanel1=20
>                     *myLoadPanel1=20
>     etc.=20
>     oh, and you could add printing, and...=20
>=20
> Cheers,=20
> Richard Bennett=20
>=20
> ma...@ri...=20
> www.richardinfo.com=20
> (Everything running on, and ported to the 19/12/2000 snapshot=20
> of DynAPI2)=20
>=20
>=20
> ----- Original Message -----=20
> From: "Pascal Bestebroer" <pa...@dy...>=20
> To: "Dev" <dyn...@li...>=20
> Sent: Sunday, January 21, 2001 2:58 PM=20
> Subject: [Dynapi-Dev] Oversight=20
>=20
>=20
> > Played "abit" with Martin Str=F6m 's console code, and got=20
> some nice ideas=20
> on=20
> > how to enhance it.=20
> > See the attached result.=20
> >=20
> > Unzip this package into a sub directory of your DynAPI code=20
> (eg. into the=20
> > src/ directory), and add the following two lines to your=20
> code for some=20
> great=20
> > debuggin tools:=20
> >=20
> > DynAPI.include('oversight.js','../src/oversight')=20
> >=20
> > and then in the DynAPI.onLoad, add the first line:=20
> >=20
> > Oversight.run('../src/oversight')=20
> >=20
> > where the '../src/oversight' is the path of your Oversight=20
> root folder.=20
> >=20
> > I haven't done much on errorhandling yet so be carefull,=20
> but currently you=20
> > have the=20
> > following tools:=20
> >=20
> > * Add watch=20
> >   Adds a property to the watcher.. the watcher will then=20
> display the value=20
> > of that property.=20
> >   For example, try adding a watch for myLayer.x  and make the layer=20
> > dragable..=20
> >=20
> > * Delete watch=20
> >   Deletes the property or variable from the watcher list..=20
> no real need=20
> for=20
> > this, every property=20
> >   will have a DEL link in the watcher window, to remove=20
> it.. saves typing=20
> >=20
> > * Dump object=20
> >   Dumps the specified object and it's properties/methods..=20
> also creating=20
> > dynamic hyperlinks for=20
> >   all child objects.=20
> >=20
> > * Show value=20
> >   Displays the value of the specified variable or property=20
> (not watching,=20
> > just printin it once)=20
> >=20
> > * Execute code=20
> >   Will execute any code you type in it.. Basically this=20
> allows you to=20
> create=20
> > DynLayer, move existing=20
> >   DynLayers/widgets, etc,etc,etc.=20
> >=20
> > I want to enhance the Execute code, so that it displays a=20
> memo field so in=20
> > which you can type more lines=20
> > at once.. making it a runtime editor.=20
> >=20
> > I think that when we create more of these types of tools, that the=20
> > DynBuilder as described by Henrik is actually possible as a=20
> Webapplication.=20
> >=20
> > I've only tested this stuff on IE5 and NS4.. and works=20
> under both browsers=20
> > perfectly.=20
> > Let me know of any ideas, comments, flames, rock throwing, etc..=20
> >=20
> > cya,=20
> >=20
> > Pascal Bestebroer=20
> > pa...@dy...=20
> > http://www.dynamic-core.net <http://www.dynamic-core.net> =20
> >=20
>=20
>=20
> _______________________________________________=20
> Dynapi-Dev mailing list=20
> Dyn...@li...=20
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
<http://lists.sourceforge.net/lists/listinfo/dynapi-dev> =20
>=20
_______________________________________________=20
Dynapi-Dev mailing list=20
Dyn...@li...=20
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
<http://lists.sourceforge.net/lists/listinfo/dynapi-dev>=20
--=20
Michael Pemberton=20
mp...@ph...=20
ICQ: 12107010=20
=20

Re: [Dynapi-Dev] Oversight (Code generation)

[Jared N. <ja...@aa...>]

Oversight is amazing! :o)

RE: [Dynapi-Dev] Oversight (Code generation)

[Pascal <pb...@oi...>]

Yep, that's basically all.. the only thing do is create a recursive function
of some sort, that walks thru all layers and child layers, and also generate
the correct addChild() calls, and all EventListeners (can be done using the
eventlisteners array).
 
The only problem still remaining is the fetching of real javascript variable
names... not sure if these are part of the DOM somewhere.. For a wysiwyg
editor it wouldn't be a problem, you could generate your own variable
names.. but for existing code you would have to use the real variable names
to not screw up existing code.
 
I also want these modules not extending the DynLayer or other DynAPI
objects, but rather have there own functions to handle these things..
 
cya,

Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Michael Pemberton
Verzonden: maandag 22 januari 2001 16:38
Aan: dyn...@li...
Onderwerp: Re: [Dynapi-Dev] Oversight (Code generation)


I was mucking around with this last night.  the attached file is one method
of doing it.
Just include the attached file and call layerName.generateCode() this should
return a copy of the initialisation command for the layer.

Pascal wrote:

Some secondary values are callable, but certain arrays will give problems
(I'm trying to fix that).

I'm not sure if I can retrieve variable names (anyone with an idea on that
one?) But I am planning on creating an extra module like Oversight, which
reads the DynAPI tree of objects (dynapi.document and all child layers) and
regenarets correct code for it.. This would be the first step for wysiwyg
editing.. simple attach dragevent listeners to every layer on screen so that
they can be placed, call the code-generator and you have your wysiwyg editor

Also another idea I'm having is including a better object watcher to
Oversight.. like the one found in Delph, Visual basic ,etc.. a window
showing all properties and values, make them editable and you have easy
access to every object, making the Dump Object obsolete.

cya,

Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [ mailto:dyn...@li...]Namens Richard Bennett
> Verzonden: maandag 22 januari 2001 0:42
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Oversight
>
>
> Hi,
> This was another amazing job, both of you, I'll add it to
> every example on
> my site with the next release,
> and have it called from a link instead of my DynAPIDiagnose.
> A few points:
>     you probably know dumping the secondary values from the hyperlinks
> doesn't work yet.
>     Is it possible to get a clickable list of the objects on
> the page by the
> name they were defined by, like this:
>
>     Available objects on this page:
>     * MyLayer
>             *MyChildLayer
>
>     * SkinWindow1
>             *myPushPanel1
>                     *myLoadPanel1
>     etc.
>     oh, and you could add printing, and...
>
> Cheers,
> Richard Bennett
>
> ma...@ri...
> www.richardinfo.com
> (Everything running on, and ported to the 19/12/2000 snapshot
> of DynAPI2)
>
>
> ----- Original Message -----
> From: "Pascal Bestebroer" <pa...@dy...>
> To: "Dev" <dyn...@li...>
> Sent: Sunday, January 21, 2001 2:58 PM
> Subject: [Dynapi-Dev] Oversight
>
>
> > Played "abit" with Martin Ström 's console code, and got
> some nice ideas
> on
> > how to enhance it.
> > See the attached result.
> >
> > Unzip this package into a sub directory of your DynAPI code
> (eg. into the
> > src/ directory), and add the following two lines to your
> code for some
> great
> > debuggin tools:
> >
> > DynAPI.include('oversight.js','../src/oversight')
> >
> > and then in the DynAPI.onLoad, add the first line:
> >
> > Oversight.run('../src/oversight')
> >
> > where the '../src/oversight' is the path of your Oversight
> root folder.
> >
> > I haven't done much on errorhandling yet so be carefull,
> but currently you
> > have the
> > following tools:
> >
> > * Add watch
> >   Adds a property to the watcher.. the watcher will then
> display the value
> > of that property.
> >   For example, try adding a watch for myLayer.x  and make the layer
> > dragable..
> >
> > * Delete watch
> >   Deletes the property or variable from the watcher list..
> no real need
> for
> > this, every property
> >   will have a DEL link in the watcher window, to remove
> it.. saves typing
> >
> > * Dump object
> >   Dumps the specified object and it's properties/methods..
> also creating
> > dynamic hyperlinks for
> >   all child objects.
> >
> > * Show value
> >   Displays the value of the specified variable or property
> (not watching,
> > just printin it once)
> >
> > * Execute code
> >   Will execute any code you type in it.. Basically this
> allows you to
> create
> > DynLayer, move existing
> >   DynLayers/widgets, etc,etc,etc.
> >
> > I want to enhance the Execute code, so that it displays a
> memo field so in
> > which you can type more lines
> > at once.. making it a runtime editor.
> >
> > I think that when we create more of these types of tools, that the
> > DynBuilder as described by Henrik is actually possible as a
> Webapplication.
> >
> > I've only tested this stuff on IE5 and NS4.. and works
> under both browsers
> > perfectly.
> > Let me know of any ideas, comments, flames, rock throwing, etc..
> >
> > cya,
> >
> > Pascal Bestebroer
> > pa...@dy...
> > http://www.dynamic-core.net
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

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

--
Michael Pemberton
mp...@ph...
ICQ: 12107010
 

RE: [Dynapi-Dev] ns6 loadpanel update and dynlayer suggestions...

[Cameron H. <ca...@bi...>]

make sure you have to right one, i posted two to the list. the first didn't
do autoresize, but the second does (kind of).

it's a work in progress and isn't quite perfect yet.

at the moment, what ns6 does is load the content into a hidden iframe, and
then gets the html and set's the innerHTML of the loadpanel to the new HTML.
If I try and get the size of the loadpanel after I've set the HTML, I can
only get the size of the visible loadpanel, not the full size of the
content. What I've done to get around this is get the size of the IFRAME
before I destroy it. This kind of works, but it's not the real content size
only an estimate. I don't actually know how to get the correct content
height/width of a layer in NS6. Does anyone else out there know?

Cameron.

> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of francesco
> AGATI
> Sent: 22 January 2001 15:34
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev] ns6 loadpanel update and dynlayer
> suggestions...
>
>
> on netscape 6 the resize of loadpanel do not function
>
>
> franesco
>
> ----- Original Message -----
> From: "Cameron Hart" <cam...@ya...>
> To: <dyn...@li...>
> Sent: Thursday, January 18, 2001 12:33 PM
> Subject: [Dynapi-Dev] ns6 loadpanel update and dynlayer suggestions...
>
>
> > I've attached an updated loadpanel with Netscape 6
> > support. I've got the Autoresize working. There are
> > still some issues though. For one, css styles are not
> > being applied to whatever's being loaded into
> > LoadPanel. I have no idea why not. Images aren't
> > always being loaded, this is also a problem with IE.
> >
> > Apart from the NS6 modifications, I've added a 'false'
> > parameter to all setHTML calls, as I believe LoadPanel
> > should not invoke load events unless something is
> > actually loaded.
> >
> > I've also got some suggested updates for dynlayer.js.
> > The first is to setHTML, I've added the noevent check
> > to the beforeload event invocation. Also, I've moved
> > this.elm.innerHTML into the else block because this
> > was setting the HTML twice in NS6, and I don't think
> > NS4 needs innerHTML to be set?
> >
> > 423,424c423
> > < this.invokeEvent("beforeload");
> > < this.elm.innerHTML=html;
> > ---
> > > if (noevt!=false) this.invokeEvent("beforeload");
> > 441c440,441
> > < else

> > ---
> > > else {
> > > this.elm.innerHTML=html;
> >
> > I've changed getContentWidth and getContentHeight to
> > support NS6, although I haven't really tested this bit
> > properly so I'm not sure that it works:
> >
> > 485c485,489
> > < return this.elm==null? 0 : (is.ns4? this.doc.width
> > : parseInt(this.elm.scrollWidth));
> > ---
> > > if (this.elm==null) return 0;
> > > else if (is.ns4) return this.doc.width;
> > > else if (is.ns5) return this.elm.offsetWidth;
> > > else return parseInt(this.elm.scrollWidth);
> > > // return this.elm==null? 0 : (is.ns4?
> > this.doc.width : parseInt(this.elm.scrollWidth));
> > 488c492,496
> > < return this.elm==null? 0 : (is.ns4? this.doc.height
> > : parseInt(this.elm.scrollHeight));
> > ---
> > > if (this.elm==null) return 0;
> > > else if (is.ns4) return this.doc.height;
> > > else if (is.ns5) return this.elm.offsetHeight;
> > > else return parseInt(this.elm.scrollHeight);
> > > // return this.elm==null? 0 : (is.ns4?
> > this.doc.height : parseInt(this.elm.scrollHeight));
> >
> > If there aren't any problems with these changes, I'd
> > like to add the NS6 enabled LoadPanel to CVS, and the
> > changes to setHTML.
> >
> > Cheers
> >
> >
> > Cameron.
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Get email at your own domain with Yahoo! Mail.
> > http://personal.mail.yahoo.com/
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re: [Dynapi-Dev] Oversight (Code generation)

[Michael P. <mp...@ph...>]

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I was mucking around with this last night.&nbsp; the attached file is one
method of doing it.
<br>Just include the attached file and call <i>layerName</i>.generateCode()
this should return a copy of the initialisation command for the layer.
<p>Pascal wrote:
<blockquote TYPE=CITE>Some secondary values are callable, but certain arrays
will give problems
<br>(I'm trying to fix that).
<p>I'm not sure if I can retrieve variable names (anyone with an idea on
that
<br>one?) But I am planning on creating an extra module like Oversight,
which
<br>reads the DynAPI tree of objects (dynapi.document and all child layers)
and
<br>regenarets correct code for it.. This would be the first step for wysiwyg
<br>editing.. simple attach dragevent listeners to every layer on screen
so that
<br>they can be placed, call the code-generator and you have your wysiwyg
editor
<p>Also another idea I'm having is including a better object watcher to
<br>Oversight.. like the one found in Delph, Visual basic ,etc.. a window
<br>showing all properties and values, make them editable and you have
easy
<br>access to every object, making the Dump Object obsolete.
<p>cya,
<p>Pascal Bestebroer (pb...@oi...)
<br>Software ontwikkelaar
<br>Oberon Informatiesystemen b.v.
<br><a href="http://www.oibv.com">http://www.oibv.com</a>
<p>> -----Oorspronkelijk bericht-----
<br>> Van: dyn...@li...
<br>> [<a href="mailto:dyn...@li...">mailto:dyn...@li...</a>]Namens
Richard Bennett
<br>> Verzonden: maandag 22 januari 2001 0:42
<br>> Aan: dyn...@li...
<br>> Onderwerp: Re: [Dynapi-Dev] Oversight
<br>>
<br>>
<br>> Hi,
<br>> This was another amazing job, both of you, I'll add it to
<br>> every example on
<br>> my site with the next release,
<br>> and have it called from a link instead of my DynAPIDiagnose.
<br>> A few points:
<br>>&nbsp;&nbsp;&nbsp;&nbsp; you probably know dumping the secondary values
from the hyperlinks
<br>> doesn't work yet.
<br>>&nbsp;&nbsp;&nbsp;&nbsp; Is it possible to get a clickable list of
the objects on
<br>> the page by the
<br>> name they were defined by, like this:
<br>>
<br>>&nbsp;&nbsp;&nbsp;&nbsp; Available objects on this page:
<br>>&nbsp;&nbsp;&nbsp;&nbsp; * MyLayer
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
*MyChildLayer
<br>>
<br>>&nbsp;&nbsp;&nbsp;&nbsp; * SkinWindow1
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
*myPushPanel1
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
*myLoadPanel1
<br>>&nbsp;&nbsp;&nbsp;&nbsp; etc.
<br>>&nbsp;&nbsp;&nbsp;&nbsp; oh, and you could add printing, and...
<br>>
<br>> Cheers,
<br>> Richard Bennett
<br>>
<br>> ma...@ri...
<br>> www.richardinfo.com
<br>> (Everything running on, and ported to the 19/12/2000 snapshot
<br>> of DynAPI2)
<br>>
<br>>
<br>> ----- Original Message -----
<br>> From: "Pascal Bestebroer" &lt;pa...@dy...>
<br>> To: "Dev" &lt;dyn...@li...>
<br>> Sent: Sunday, January 21, 2001 2:58 PM
<br>> Subject: [Dynapi-Dev] Oversight
<br>>
<br>>
<br>> > Played "abit" with Martin Str&ouml;m 's console code, and got
<br>> some nice ideas
<br>> on
<br>> > how to enhance it.
<br>> > See the attached result.
<br>> >
<br>> > Unzip this package into a sub directory of your DynAPI code
<br>> (eg. into the
<br>> > src/ directory), and add the following two lines to your
<br>> code for some
<br>> great
<br>> > debuggin tools:
<br>> >
<br>> > DynAPI.include('oversight.js','../src/oversight')
<br>> >
<br>> > and then in the DynAPI.onLoad, add the first line:
<br>> >
<br>> > Oversight.run('../src/oversight')
<br>> >
<br>> > where the '../src/oversight' is the path of your Oversight
<br>> root folder.
<br>> >
<br>> > I haven't done much on errorhandling yet so be carefull,
<br>> but currently you
<br>> > have the
<br>> > following tools:
<br>> >
<br>> > * Add watch
<br>> >&nbsp;&nbsp; Adds a property to the watcher.. the watcher will then
<br>> display the value
<br>> > of that property.
<br>> >&nbsp;&nbsp; For example, try adding a watch for myLayer.x&nbsp;
and make the layer
<br>> > dragable..
<br>> >
<br>> > * Delete watch
<br>> >&nbsp;&nbsp; Deletes the property or variable from the watcher list..
<br>> no real need
<br>> for
<br>> > this, every property
<br>> >&nbsp;&nbsp; will have a DEL link in the watcher window, to remove
<br>> it.. saves typing
<br>> >
<br>> > * Dump object
<br>> >&nbsp;&nbsp; Dumps the specified object and it's properties/methods..
<br>> also creating
<br>> > dynamic hyperlinks for
<br>> >&nbsp;&nbsp; all child objects.
<br>> >
<br>> > * Show value
<br>> >&nbsp;&nbsp; Displays the value of the specified variable or property
<br>> (not watching,
<br>> > just printin it once)
<br>> >
<br>> > * Execute code
<br>> >&nbsp;&nbsp; Will execute any code you type in it.. Basically this
<br>> allows you to
<br>> create
<br>> > DynLayer, move existing
<br>> >&nbsp;&nbsp; DynLayers/widgets, etc,etc,etc.
<br>> >
<br>> > I want to enhance the Execute code, so that it displays a
<br>> memo field so in
<br>> > which you can type more lines
<br>> > at once.. making it a runtime editor.
<br>> >
<br>> > I think that when we create more of these types of tools, that
the
<br>> > DynBuilder as described by Henrik is actually possible as a
<br>> Webapplication.
<br>> >
<br>> > I've only tested this stuff on IE5 and NS4.. and works
<br>> under both browsers
<br>> > perfectly.
<br>> > Let me know of any ideas, comments, flames, rock throwing, etc..
<br>> >
<br>> > cya,
<br>> >
<br>> > Pascal Bestebroer
<br>> > pa...@dy...
<br>> > <a href="http://www.dynamic-core.net">http://www.dynamic-core.net</a>
<br>> >
<br>>
<br>>
<br>> _______________________________________________
<br>> Dynapi-Dev mailing list
<br>> Dyn...@li...
<br>> <a href="http://lists.sourceforge.net/lists/listinfo/dynapi-dev">http://lists.sourceforge.net/lists/listinfo/dynapi-dev</a>
<br>>
<p>_______________________________________________
<br>Dynapi-Dev mailing list
<br>Dyn...@li...
<br><a href="http://lists.sourceforge.net/lists/listinfo/dynapi-dev">http://lists.sourceforge.net/lists/listinfo/dynapi-dev</a></blockquote>

<p>--
<br>Michael Pemberton
<br>mp...@ph...
<br>ICQ: 12107010
<br>&nbsp;</html>

RE: [Dynapi-Dev] Oversight

[Pascal <pb...@oi...>]

Some secondary values are callable, but certain arrays will give problems
(I'm trying to fix that).

I'm not sure if I can retrieve variable names (anyone with an idea on that
one?) But I am planning on creating an extra module like Oversight, which
reads the DynAPI tree of objects (dynapi.document and all child layers) and
regenarets correct code for it.. This would be the first step for wysiwyg
editing.. simple attach dragevent listeners to every layer on screen so that
they can be placed, call the code-generator and you have your wysiwyg editor

Also another idea I'm having is including a better object watcher to
Oversight.. like the one found in Delph, Visual basic ,etc.. a window
showing all properties and values, make them editable and you have easy
access to every object, making the Dump Object obsolete.


cya,

Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Richard Bennett
> Verzonden: maandag 22 januari 2001 0:42
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Oversight
>
>
> Hi,
> This was another amazing job, both of you, I'll add it to
> every example on
> my site with the next release,
> and have it called from a link instead of my DynAPIDiagnose.
> A few points:
>     you probably know dumping the secondary values from the hyperlinks
> doesn't work yet.
>     Is it possible to get a clickable list of the objects on
> the page by the
> name they were defined by, like this:
>
>     Available objects on this page:
>     * MyLayer
>             *MyChildLayer
>
>     * SkinWindow1
>             *myPushPanel1
>                     *myLoadPanel1
>     etc.
>     oh, and you could add printing, and...
>
> Cheers,
> Richard Bennett
>
> ma...@ri...
> www.richardinfo.com
> (Everything running on, and ported to the 19/12/2000 snapshot
> of DynAPI2)
>
>
> ----- Original Message -----
> From: "Pascal Bestebroer" <pa...@dy...>
> To: "Dev" <dyn...@li...>
> Sent: Sunday, January 21, 2001 2:58 PM
> Subject: [Dynapi-Dev] Oversight
>
>
> > Played "abit" with Martin Ström 's console code, and got
> some nice ideas
> on
> > how to enhance it.
> > See the attached result.
> >
> > Unzip this package into a sub directory of your DynAPI code
> (eg. into the
> > src/ directory), and add the following two lines to your
> code for some
> great
> > debuggin tools:
> >
> > DynAPI.include('oversight.js','../src/oversight')
> >
> > and then in the DynAPI.onLoad, add the first line:
> >
> > Oversight.run('../src/oversight')
> >
> > where the '../src/oversight' is the path of your Oversight
> root folder.
> >
> > I haven't done much on errorhandling yet so be carefull,
> but currently you
> > have the
> > following tools:
> >
> > * Add watch
> >   Adds a property to the watcher.. the watcher will then
> display the value
> > of that property.
> >   For example, try adding a watch for myLayer.x  and make the layer
> > dragable..
> >
> > * Delete watch
> >   Deletes the property or variable from the watcher list..
> no real need
> for
> > this, every property
> >   will have a DEL link in the watcher window, to remove
> it.. saves typing
> >
> > * Dump object
> >   Dumps the specified object and it's properties/methods..
> also creating
> > dynamic hyperlinks for
> >   all child objects.
> >
> > * Show value
> >   Displays the value of the specified variable or property
> (not watching,
> > just printin it once)
> >
> > * Execute code
> >   Will execute any code you type in it.. Basically this
> allows you to
> create
> > DynLayer, move existing
> >   DynLayers/widgets, etc,etc,etc.
> >
> > I want to enhance the Execute code, so that it displays a
> memo field so in
> > which you can type more lines
> > at once.. making it a runtime editor.
> >
> > I think that when we create more of these types of tools, that the
> > DynBuilder as described by Henrik is actually possible as a
> Webapplication.
> >
> > I've only tested this stuff on IE5 and NS4.. and works
> under both browsers
> > perfectly.
> > Let me know of any ideas, comments, flames, rock throwing, etc..
> >
> > cya,
> >
> > Pascal Bestebroer
> > pa...@dy...
> > http://www.dynamic-core.net
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

Re: [Dynapi-Dev] Tables and previews

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

Please use the widgetdev list for discussion of your widget.

-- 
// Robert Rainwater

On 1/22/2001, 5:50:18 AM EST, Eytan wrote about "[Dynapi-Dev] Tables and previews":

> Hi,
> I have now a working table with borders. And the cells properties is a two-dimensional array of labels.
> It is included. BTW I have found a really weird bug and am about to submit it.
> 8an


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

Re: [Dynapi-Dev] ns6 loadpanel update and dynlayer suggestions...

[francesco A. <fa...@we...>]

on netscape 6 the resize of loadpanel do not function


franesco

----- Original Message ----- 
From: "Cameron Hart" <cam...@ya...>
To: <dyn...@li...>
Sent: Thursday, January 18, 2001 12:33 PM
Subject: [Dynapi-Dev] ns6 loadpanel update and dynlayer suggestions...


> I've attached an updated loadpanel with Netscape 6
> support. I've got the Autoresize working. There are
> still some issues though. For one, css styles are not
> being applied to whatever's being loaded into
> LoadPanel. I have no idea why not. Images aren't
> always being loaded, this is also a problem with IE.
> 
> Apart from the NS6 modifications, I've added a 'false'
> parameter to all setHTML calls, as I believe LoadPanel
> should not invoke load events unless something is
> actually loaded.
> 
> I've also got some suggested updates for dynlayer.js.
> The first is to setHTML, I've added the noevent check
> to the beforeload event invocation. Also, I've moved
> this.elm.innerHTML into the else block because this
> was setting the HTML twice in NS6, and I don't think
> NS4 needs innerHTML to be set?
> 
> 423,424c423
> < this.invokeEvent("beforeload");
> < this.elm.innerHTML=html;
> ---
> > if (noevt!=false) this.invokeEvent("beforeload");
> 441c440,441
> < else { 
> ---
> > else {
> > this.elm.innerHTML=html;
> 
> I've changed getContentWidth and getContentHeight to
> support NS6, although I haven't really tested this bit
> properly so I'm not sure that it works:
> 
> 485c485,489
> < return this.elm==null? 0 : (is.ns4? this.doc.width
> : parseInt(this.elm.scrollWidth));
> ---
> > if (this.elm==null) return 0;
> > else if (is.ns4) return this.doc.width;
> > else if (is.ns5) return this.elm.offsetWidth;
> > else return parseInt(this.elm.scrollWidth);
> > // return this.elm==null? 0 : (is.ns4?
> this.doc.width : parseInt(this.elm.scrollWidth));
> 488c492,496
> < return this.elm==null? 0 : (is.ns4? this.doc.height
> : parseInt(this.elm.scrollHeight));
> ---
> > if (this.elm==null) return 0;
> > else if (is.ns4) return this.doc.height;
> > else if (is.ns5) return this.elm.offsetHeight;
> > else return parseInt(this.elm.scrollHeight);
> > // return this.elm==null? 0 : (is.ns4?
> this.doc.height : parseInt(this.elm.scrollHeight));
> 
> If there aren't any problems with these changes, I'd
> like to add the NS6 enabled LoadPanel to CVS, and the
> changes to setHTML.
> 
> Cheers
> 
> 
> Cameron.
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail. 
> http://personal.mail.yahoo.com/

[Dynapi-Dev] [Patch #103359] NS6 event fixes

[<no...@so...>]

Patch #103359 has been updated. 

Project: dynapi
Category: DynAPI-Event
Status: Open
Submitted by: camhart
Assigned to : nobody
Summary: NS6 event fixes

-------------------------------------------------------
For more info, visit:

http://sourceforge.net/patch/?func=detailpatch&patch_id=103359&group_id=5757

[Dynapi-Dev] [Patch #103358] NS6 fixes to inline.js

[<no...@so...>]

Patch #103358 has been updated. 

Project: dynapi
Category: DynAPI-Ext
Status: Open
Submitted by: camhart
Assigned to : nobody
Summary: NS6 fixes to inline.js

-------------------------------------------------------
For more info, visit:

http://sourceforge.net/patch/?func=detailpatch&patch_id=103358&group_id=5757

[Dynapi-Dev] [Bug #129663] IE 5.0 crashes

[<no...@so...>]

Bug #129663, was updated on 2001-Jan-22 02:55
Here is a current snapshot of the bug.

Project: DynAPI 2
Category: Core API
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: eytanh
Assigned to : nobody
Summary: IE 5.0 crashes

Details: Using my table (submitted to the dev list) and putting it in a
scroll-pane IE 5.0 crashes with access violation! This does not happen in
5.5 or NN4.7.

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=129663&group_id=5757

[Dynapi-Dev] Tables and previews

[Eytan H. <ey...@tr...>]

Hi,
I have now a working table with borders. And the cells properties is a =
two-dimensional array of labels.
It is included. BTW I have found a really weird bug and am about to =
submit it.
8an

Re: Re[2]: [Dynapi-Dev] [Bug #129602] DynLayer methods don't effect elements

[Eytan H. <ey...@tr...>]

I've added those lines and it still doesn't help.

8an

[Dynapi-Dev] [Dynapi-Dev]

[Raymond S. <dst...@or...>]

ARGGGGGGGGGGGGGGGGG!

Ok feel better now.  Talk to you lads (and ladets) later.

DS

[Dynapi-Dev] To all; Re drag events. (and other events)

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

I have seen a lot of question latly which should be cleared up with the =
following.

I found that when dragging my toolbar on a slower machine that =
eveerything got VERY choppy.

So I applied and old Visual Basic fix and everything smothed out.

The premis of the fix is that an event can be called while the code of =
the same event is still executing from the last call.

So here is what I did.

In the tool bar I added a property called dragging.

this is treated as a boolean switch and is used as shown below:

 l.ondragmove=3Dfunction(e) {
  e.setBubble(false);
  var o=3De.getTarget();
  if (!o.dragging){
   o.dragging=3Dtrue;
   o.moveTo(e.pageX-10,e.pageY-10);
   o.dragging=3Dfalse;
  }
 }

so.. if the code from the previous call is still executeing =
(o.dragging=3Dtrue) then don't try to execute the code again.

This has made the dragging of my toolbar MUCH more smoother, and I =
believe that such a=20
switch can be used to clear up MANY similar event-based problems..

Such as in a resize event, or a mousemove event.

Later.
Doug Melvin

Re: [Dynapi-Dev] Oversight

[Richard B. <ma...@ri...>]

Hi,
This was another amazing job, both of you, I'll add it to every example on
my site with the next release,
and have it called from a link instead of my DynAPIDiagnose.
A few points:
    you probably know dumping the secondary values from the hyperlinks
doesn't work yet.
    Is it possible to get a clickable list of the objects on the page by the
name they were defined by, like this:

    Available objects on this page:
    * MyLayer
            *MyChildLayer

    * SkinWindow1
            *myPushPanel1
                    *myLoadPanel1
    etc.
    oh, and you could add printing, and...

Cheers,
Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)


----- Original Message -----
From: "Pascal Bestebroer" <pa...@dy...>
To: "Dev" <dyn...@li...>
Sent: Sunday, January 21, 2001 2:58 PM
Subject: [Dynapi-Dev] Oversight


> Played "abit" with Martin Ström 's console code, and got some nice ideas
on
> how to enhance it.
> See the attached result.
>
> Unzip this package into a sub directory of your DynAPI code (eg. into the
> src/ directory), and add the following two lines to your code for some
great
> debuggin tools:
>
> DynAPI.include('oversight.js','../src/oversight')
>
> and then in the DynAPI.onLoad, add the first line:
>
> Oversight.run('../src/oversight')
>
> where the '../src/oversight' is the path of your Oversight root folder.
>
> I haven't done much on errorhandling yet so be carefull, but currently you
> have the
> following tools:
>
> * Add watch
>   Adds a property to the watcher.. the watcher will then display the value
> of that property.
>   For example, try adding a watch for myLayer.x  and make the layer
> dragable..
>
> * Delete watch
>   Deletes the property or variable from the watcher list.. no real need
for
> this, every property
>   will have a DEL link in the watcher window, to remove it.. saves typing
>
> * Dump object
>   Dumps the specified object and it's properties/methods.. also creating
> dynamic hyperlinks for
>   all child objects.
>
> * Show value
>   Displays the value of the specified variable or property (not watching,
> just printin it once)
>
> * Execute code
>   Will execute any code you type in it.. Basically this allows you to
create
> DynLayer, move existing
>   DynLayers/widgets, etc,etc,etc.
>
> I want to enhance the Execute code, so that it displays a memo field so in
> which you can type more lines
> at once.. making it a runtime editor.
>
> I think that when we create more of these types of tools, that the
> DynBuilder as described by Henrik is actually possible as a
Webapplication.
>
> I've only tested this stuff on IE5 and NS4.. and works under both browsers
> perfectly.
> Let me know of any ideas, comments, flames, rock throwing, etc..
>
> cya,
>
> Pascal Bestebroer
> pa...@dy...
> http://www.dynamic-core.net
>

Re: [Dynapi-Dev] Weird Error

[labCoat <la...@xe...>]

First of all, 

I would like to say that I am back from hiding :-) -- I know that I have been out of the loop for a while and have not been able to keep up with what is going on too much, but after looking over the newest (CVS) release, and reading 987,345,276,765,575 emails :-), I think that I am up to speed, and would like to start contributing again!

now to the problem at hand...

I have run into the same error before.

I had a layer ("layerA") that had a child layer ("layerA_child"). "layerA" was already added to the document, and when I removed the layer from the document and then added it to another layer, I got the
error that "layerA_child" was already added to the document. 

The problem is with the removeChild/removeFromParent methods of the DynLayer. When you call a remove method of a layer, one of the things that it does is to remove the specified layer from the all array, and add it to the unassigned array, but it never does that with it's children. 

I came up with a quick-fix (don't know how good it works in all situations, but I can't think of any where it won't work :-)).

I added the DynLayer method:

<!--//
/*

DynLayer.prototype.removeAllChildren=function() {
    var child;
    for (var i in this.children) {
        child=this.children[i];        
        child.removeAllChildren();
        DynAPI.removeFromArray(this.dyndoc.all,child,true);
        DynLayer.unassigned[child.id]=child;
    }
};

*/
//-->

And then, I call removeAllChildren from removeChild, as shown below. 

<!--//
/*

DynLayer.prototype.removeChild=function() {
    var child;
    for (var a=0; a<arguments.length; a++) {
        child=arguments[a];
        
        // FIX: MAKE CALL HERE
        child.removeAllChildren();
        //END FIX
        
        if (child.parent==this) {
            DynAPI.removeFromArray(this.children,child);
            DynAPI.removeFromArray(this.dyndoc.all,child,true);
            DynLayer.unassigned[child.id]=child;
            DynLayer.deleteElement(child);
            child.parent=null;
            child.isChild=false;
        }
    }
	return arguments[arguments.length-1];
};

*/
//-->

It takes all of the children layers of the 'removed' layer, and also removes them from the all array, and adds them to the unassigned array, so that when you add it to a document or to another layer, you do not get that error.

Is this worthy of a patch, or just a duct-tape fix?

If there is a better way to do this, I would appriciate some feedback :-)

--proteanman


On Sun, 21 January 2001, "Eytan Heidingsfeld" wrote:

> 
> Hi,
> I've been working on something both at home and at work. I brought these
> files home and suddenly get these errors JSDynlayer0 is already in
> DynDocument you must remove it first and also elm.all is undefined. What is
> going on??
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re[2]: [Dynapi-Dev] [Bug #129602] DynLayer methods don't effect elements

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

Also, I forgot to add that Table is a reserved word, so you may have
some namespace problems.  You may want to rename it to something like
DynTable.

-- 
// Robert Rainwater

On 1/21/2001, 4:09:42 PM EST, Eytan wrote about "[Dynapi-Dev] [Bug #129602] DynLayer methods don't effect elements":

> I am using the correct methods.
> For an explicit example please refer to the attached files. You must add the
> table.js file to your gui folder and put the testtable.htm file in one
> folder inside the root.


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

Re[2]: [Dynapi-Dev] [Bug #129602] DynLayer methods don't effect elements

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

The first thing that I noticed was that you failed to call the
DynLayer constructor.  You need this:

function Table(rows,cols){
  this.DynLayer = DynLayer
  this.DynLayer()
  ....

This is essential for correct subclassing (the prototype setting is
not enough).

-- 
// Robert Rainwater

On 1/21/2001, 4:09:42 PM EST, Eytan wrote about "[Dynapi-Dev] [Bug #129602] DynLayer methods don't effect elements":

> I am using the correct methods.
> For an explicit example please refer to the attached files. You must add the
> table.js file to your gui folder and put the testtable.htm file in one
> folder inside the root.


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

RE: [Dynapi-Dev] [Bug #129602] DynLayer methods don't effect elements

[Eytan H. <ey...@tr...>]

I am using the correct methods.
For an explicit example please refer to the attached files. You must add the
table.js file to your gui folder and put the testtable.htm file in one
folder inside the root.

Re: [Dynapi-Dev] [Bug #129602] Dynlayers methods dont effect elements

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

Could you be more specific.  I have no way of testing this without any
details.  Are you using dynlayer methods to set the properties?  For
example:
mylayer.x = 4 // does not do anything

You must use the correct methods.

-- 
// Robert Rainwater

On 1/21/2001, 3:26:28 PM EST, noreply wrote about "[Dynapi-Dev] [Bug #129602] Dynlayers methods dont effect elements":

> Bug #129602, was updated on 2001-Jan-21 12:26
> Here is a current snapshot of the bug.

> Project: DynAPI 2
> Category: Core API
> Status: Open
> Resolution: None
> Bug Group: None
> Priority: 5
> Submitted by: eytanh
> Assigned to : nobody
> Summary: Dynlayers methods dont effect elements

> Details: Now I have decided to call it a bug.
> I have my table widget in it I create cells. All the cells are fine, there
> properties are set to the right ones but the actual elements aren't. I have
> checked this by using breakpoints with InterDev.
> If anyone wants the code email me.

> For detailed info, follow this link:
> http://sourceforge.net/bugs/?func=detailbug&bug_id=129602&group_id=5757

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


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

[Dynapi-Dev] [Bug #129602] Dynlayers methods dont effect elements

[<no...@so...>]

Bug #129602, was updated on 2001-Jan-21 12:26
Here is a current snapshot of the bug.

Project: DynAPI 2
Category: Core API
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: eytanh
Assigned to : nobody
Summary: Dynlayers methods dont effect elements

Details: Now I have decided to call it a bug.
I have my table widget in it I create cells. All the cells are fine, there
properties are set to the right ones but the actual elements aren't. I have
checked this by using breakpoints with InterDev.
If anyone wants the code email me.

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=129602&group_id=5757