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

[Dynapi-Dev] [ dynapi-Bugs-763598 ] DynAPI3 - IE Mac 5.2 Crashes when Refresh is clicked

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

Bugs item #763598, was opened at 2003-06-30 19:50
Message generated for change (Comment added) made by ecammit
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763598&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Timothy Ace (ecammit)
Assigned to: Nobody/Anonymous (nobody)
Summary: DynAPI3 - IE Mac 5.2 Crashes when Refresh is clicked

Initial Comment:
This can be seen most prevailently in:

dynapi3x/tshoot/drag_forms.html

The page loads fine, but it crashes the whole browser
when you press the 'Refresh' Button.

----------------------------------------------------------------------

>Comment By: Timothy Ace (ecammit)
Date: 2003-07-03 20:13

Message:
Logged In: YES 
user_id=608186

I managed to track the error to the line:

<code>this.children[this.children.length] = c;</code>

In p.addChild in file /src/api/event.js line 140.

This only crashes when there are radio buttons (without the
name attribute) and anchor tags in the html of the layer. 
There may be more elements that cause the crash, but I have
not yet found them.  I am at a total loss as to how to fix
this, as I believe it is a browser bug, and Microsoft has
vowed to stop supporting IE for the mac.

Any suggestions would be helpful.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763598&group_id=5757

Re: [Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

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

You're correct it's not yet inside CVS. I wan'ted to
submit a few other fixes as well. This fix should make
it's way into cvs over the weekend.

--
Raymond Irving

--- "SourceForge.net" <no...@so...> wrote:
> Bugs item #762495, was opened at 2003-06-28 22:31
> Message generated for change (Comment added) made by
> bs_php
> You can respond by visiting: 
>
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757
> 
> Category: DynAPI 3 API
> Group: Unverified
> Status: Open
> Resolution: Fixed
> Priority: 5
> Submitted By: Sam Blum (bs_php)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: Wrong position retured when page has been
> scrolled down.
> 
> Initial Comment:
> Reproduced the bug in IE and Mozilla 1.3
> 
> To see the effect, open the dynapi example:
> examples/dynapi.api.mouseevent.html 
> - You should see some colored layers that are
> cascaded 
> in each 
>   other in the middle of the page. 
> - On the left we have some links to turn
> mouse-events 
> on and off.
> - The debugger window should open as well.
> 
> The page contains so much info, that a standard
> scroll-
> bar should appear on the right of the browser. If
> not 
> make the browser window less high.
> 
> Now do as follows:
> A) Turn on the click/dblclick events for the blue
> layer. 
>    This is done by clicking on the 
>       "Listen to click/dblclick events -> blue ->
> on" 
>    link (see the page)
> 
> B) Then click on the blue layer top left corner and
> look 
>    at the output on the debugger window. It should
> say 
>    something like this: 
>    "click blue xy=0,0 pXY=300,200 origin=blue"
> 
>    NOTE: 
>    xy are the coordinates of the click on the blue
> layer 
>    relative to it's own top left corner. pXY are the
> 
>    absolute coordinates relative to the view (top
> left 
>    corner of the browser).
> 
> C) Now scroll down a little and click again on the
> blue 
>    layer (try to hit the same spot). Now in the
> debugger 
>    window look at the result: 
>    "click blue xy=0,-148 pXY=300,52 origin=blue"
> 
> BUG: 
>   Compare the xy result 0,0 and 0,-148. I would have
> 
>   expected to get the same result in case A) and B) 
>   for xy (the pXY results are OK). But the y axis
> has 
>   a negative number, caused by the scrolling.
>   
>   
> Side Effect Bug:  
>   Next I modified the code and set the red layer 
> to 'relative'
>   Thus, I added line:  red.setPosition('relative');
>   This will position the layers at the bottom of the
> 
>   page. Again try to repeat B) and C) (as good as
> you 
> can) 
>   and compare the results:
>     "click blue xy=8,496 pXY=308,696 origin=blue"
>     "click blue xy=8,396 pXY=308,596 origin=blue"
> 
> The effect is the same AND a *side effect* shows up:
> alway have an x offset of 8px (13px on IE). But I
> heard 
> that reletive posistioning is problematic.
> 
> -- bs_php
> 
>
----------------------------------------------------------------------
> 
> >Comment By: Sam Blum (bs_php)
> Date: 2003-07-04 00:44
> 
> Message:
> Logged In: YES 
> user_id=308859
> 
> According to the CVS on sourceforge, no updates have
> been 
> mad to mouse_dom.js in dynapi3x.
> 
> Are you using an other CVS? If so can I get access?
> 
> -- sam
> 
>
----------------------------------------------------------------------
> 
> Comment By: Raymond Irving (xwisdom)
> Date: 2003-06-30 14:55
> 
> Message:
> Logged In: YES 
> user_id=696242
> 
> Hi bs_php,
> 
> Bug verified and fixed
> 
> I've implemented your fix into the MouseEvent files
> and it 
> seems to have resolve the porblem. Many thanks for
> this fix.
> 
> --
> Raymond Irving
> 
>
----------------------------------------------------------------------
> 
> Comment By: Sam Blum (bs_php)
> Date: 2003-06-29 01:18
> 
> Message:
> Logged In: YES 
> user_id=308859
> 
> This would my suggestion for mouse_dom.js
> 
> p.getScrollX = function() {return 
> document.body.scrollTop||0};
> p.getScrollY = function() {return 
> document.body.scrollLeft||0};
> p.getX=function() {return (this.x||0)  +
> this.getScrollX()};
> p.getY=function() {return (this.y||0)  +
> this.getScrollY()};
> 
> 
> This would my suggestion for mouse_ie.js
> p.getScrollX = function() {return
> window.pageXOffset||0};
> p.getScrollY = function() {return
> window.pageYOffset||0};
> p.getX=function() {return (this.x||0)  +
> this.getScrollX()};
> p.getY=function() {return (this.y||0)  +
> this.getScrollY()};
> 
> 
> 
>
----------------------------------------------------------------------
> 
> Comment By: Sam Blum (bs_php)
> Date: 2003-06-29 00:47
> 
> Message:
> Logged In: YES 
> user_id=308859
> 
> OK here is the solution ( I know it' currently a
> hack) 
> =================================
> For Mozzila 1.3 in mouse_dom.js replace the lines:
> 
>   p.getX = function() {return this.x};
>   p.getY = function() {return this.y};
> 
> with 
> 
>   p.getX_ = function() {
>     var _x = this.x||0;
>     var _xOffset = 0;
>     if (this.ns) {
>       _xOffset = document.body.scrollTop||0;
>     }else{
>       _xOffset = window.pageXOffset||0;
>     }
>     return _x + _xOffset;
>   };
>   
>   p.getY_ = function() {
>     var _y = this.y||0;
>     var _yOffset = 0;
>     if (this.ns) {
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

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

Bugs item #762495, was opened at 2003-06-28 22:31
Message generated for change (Comment added) made by bs_php
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Category: DynAPI 3 API
Group: Unverified
Status: Open
Resolution: Fixed
Priority: 5
Submitted By: Sam Blum (bs_php)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong position retured when page has been scrolled down.

Initial Comment:
Reproduced the bug in IE and Mozilla 1.3

To see the effect, open the dynapi example:
examples/dynapi.api.mouseevent.html 
- You should see some colored layers that are cascaded 
in each 
  other in the middle of the page. 
- On the left we have some links to turn mouse-events 
on and off.
- The debugger window should open as well.

The page contains so much info, that a standard scroll-
bar should appear on the right of the browser. If not 
make the browser window less high.

Now do as follows:
A) Turn on the click/dblclick events for the blue layer. 
   This is done by clicking on the 
      "Listen to click/dblclick events -> blue -> on" 
   link (see the page)

B) Then click on the blue layer top left corner and look 
   at the output on the debugger window. It should say 
   something like this: 
   "click blue xy=0,0 pXY=300,200 origin=blue"

   NOTE: 
   xy are the coordinates of the click on the blue layer 
   relative to it's own top left corner. pXY are the 
   absolute coordinates relative to the view (top left 
   corner of the browser).

C) Now scroll down a little and click again on the blue 
   layer (try to hit the same spot). Now in the debugger 
   window look at the result: 
   "click blue xy=0,-148 pXY=300,52 origin=blue"

BUG: 
  Compare the xy result 0,0 and 0,-148. I would have 
  expected to get the same result in case A) and B) 
  for xy (the pXY results are OK). But the y axis has 
  a negative number, caused by the scrolling.
  
  
Side Effect Bug:  
  Next I modified the code and set the red layer 
to 'relative'
  Thus, I added line:  red.setPosition('relative');
  This will position the layers at the bottom of the 
  page. Again try to repeat B) and C) (as good as you 
can) 
  and compare the results:
    "click blue xy=8,496 pXY=308,696 origin=blue"
    "click blue xy=8,396 pXY=308,596 origin=blue"

The effect is the same AND a *side effect* shows up:
alway have an x offset of 8px (13px on IE). But I heard 
that reletive posistioning is problematic.

-- bs_php

----------------------------------------------------------------------

>Comment By: Sam Blum (bs_php)
Date: 2003-07-04 00:44

Message:
Logged In: YES 
user_id=308859

According to the CVS on sourceforge, no updates have been 
mad to mouse_dom.js in dynapi3x.

Are you using an other CVS? If so can I get access?

-- sam

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-06-30 14:55

Message:
Logged In: YES 
user_id=696242

Hi bs_php,

Bug verified and fixed

I've implemented your fix into the MouseEvent files and it 
seems to have resolve the porblem. Many thanks for this fix.

--
Raymond Irving

----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-29 01:18

Message:
Logged In: YES 
user_id=308859

This would my suggestion for mouse_dom.js

p.getScrollX = function() {return 
document.body.scrollTop||0};
p.getScrollY = function() {return 
document.body.scrollLeft||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};


This would my suggestion for mouse_ie.js
p.getScrollX = function() {return window.pageXOffset||0};
p.getScrollY = function() {return window.pageYOffset||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};



----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-29 00:47

Message:
Logged In: YES 
user_id=308859

OK here is the solution ( I know it' currently a hack) 
=================================
For Mozzila 1.3 in mouse_dom.js replace the lines:

  p.getX = function() {return this.x};
  p.getY = function() {return this.y};

with 

  p.getX_ = function() {
    var _x = this.x||0;
    var _xOffset = 0;
    if (this.ns) {
      _xOffset = document.body.scrollTop||0;
    }else{
      _xOffset = window.pageXOffset||0;
    }
    return _x + _xOffset;
  };
  
  p.getY_ = function() {
    var _y = this.y||0;
    var _yOffset = 0;
    if (this.ns) {
      _yOffset = document.body.scrollLeft||0;
    }else{
      _yOffset = window.pageYOffset||0;
    }
    return _y + _yOffset;
  };


NOTE: I've seen in the code that this.x and this.y are refered 
often directly (not using the getX()-methode) so there may 
more to correct then just the methods  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-765597 ] layer.setTextSelectable(false)

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

Bugs item #765597, was opened at 2003-07-03 22:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=765597&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Tiru (tiru)
Assigned to: Nobody/Anonymous (nobody)
Summary: layer.setTextSelectable(false)

Initial Comment:
Hi!

It seams like the lyr.setTextSelectable(false); is 
inherited on all layers and not just on the layer that is 
supposed(?) to be adjusted.

Try to have 2 textlayers and set the property on one of 
them and you will see.

Contact me if you need some more info
/Daniel Tiru

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=765597&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-765594 ] setTextSelectable(false)

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

Bugs item #765594, was opened at 2003-07-03 22:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=765594&group_id=5757

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Tiru (tiru)
Assigned to: Nobody/Anonymous (nobody)
Summary: setTextSelectable(false)

Initial Comment:
Hi!

It seams like the lyr.setTextSelectable(false); is 
inherited on all layers and not just on the layer that is 
supposed(?) to be adjusted.

Try to have 2 textlayers and set the property on one of 
them and you will see.

Contact me if you need some more info
/Daniel Tiru

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=765594&group_id=5757

Re: [Dynapi-Dev] Perl IOElement module & vacation

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

Sounds really great Leif. 

Hmmm... Should we convert the server-side ioelement
functions into an object? I first started out with
wsMethodName since it was easier to port and supported
many platforms. I don't think having multiple instance
of the IOElement on the server would be of any
benefit, but what have you to say about it (anyone can
answer)?

--
Raymond Irving

 

--- Leif W <war...@us...> wrote:
> Hello,
> 
> Just an update to let everyone know where I'm at. 
> First I wrote a simple
> IOElement that had some global variables and
> subroutines (functions) as a
> literal translation of the JScript ASP version, but
> I did not test it.  Then
> I decided I might as well make a Perl object of
> IOElement, so you can have a
> script with multiple instances of an IOElement class
> (but I wonder, would
> this be useful?).  But to do this, I've had to read
> the programming docs.
> >:-)  However, I'm going on vacation today.  I have
> a basic grasp of OOP in
> perl now, but still some docs to read (and re-read)
> before I know exactly
> what I'm doing.  When I get back from vacation I'll
> start working on the
> IOElement object/class/package thing for Perl, and
> I'll just try and copy
> (convert) some of the existing server-side examples
> for test programs.
> 
> Have a happy and safe 4th of July (if you're in the
> US),
> 
> Leif
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] Perl IOElement module & vacation

[Leif W <war...@us...>]

Hello,

Just an update to let everyone know where I'm at.  First I wrote a simple
IOElement that had some global variables and subroutines (functions) as a
literal translation of the JScript ASP version, but I did not test it.  Then
I decided I might as well make a Perl object of IOElement, so you can have a
script with multiple instances of an IOElement class (but I wonder, would
this be useful?).  But to do this, I've had to read the programming docs.
>:-)  However, I'm going on vacation today.  I have a basic grasp of OOP in
perl now, but still some docs to read (and re-read) before I know exactly
what I'm doing.  When I get back from vacation I'll start working on the
IOElement object/class/package thing for Perl, and I'll just try and copy
(convert) some of the existing server-side examples for test programs.

Have a happy and safe 4th of July (if you're in the US),

Leif

Fix: Re: [Dynapi-Dev] Swiper Updates

[Daniel T. <de...@ti...>]

A small error got in to the swiper there... but now it is fixed.

/Daniel

> Hi!
> 
> The bug is fixed and aswell an unreported bug that made the layer "flicker" when used a function several times. This is made by adding a variable to the dynlayer witch is called "swiperMinimized" to keep the state of the swiper first time the swiper is used for the specific layer.
> 
> Regards
> Daniel
> 
> > Hi,
> > 
> > The attached file is an update to the swiper library
> > 
> > I've renamed the inc-dec swipe values to inc-left,
> > dec-right, etc in order to be consistent with
> > top-right, bottom-left, etc
> > 
> > Bugs:
> > 
> > 1) If you were to press the dec-up or inc-left button
> > more than once the layer would scroll off the screen
> > 
> > 2) The getClip() function now returns the correct
> > values in opera v7 but there seems to be a bug with
> > it's css clip property. Is there a workaround? Is this
> > a known bug in opera?
> > 
> > 
> > --
> > Raymond Irving
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > SBC Yahoo! DSL - Now only $29.95 per month!
> > http://sbc.yahoo.com
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are available now.
> > Download today and enter to win an XBOX or Visual Studio .NET.
> > http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://www.mail-archive.com/dyn...@li.../
> > ----------------------------------------------------
> >      Name: swiper.zip
> >      Type: application/x-zip-compressed
> >  Encoding: base64
> >    Length: 5.63 KB
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> ----------------------------------------------------
>      Name: swiper.zip
>      Type: application/x-zip-compressed
>  Encoding: base64
>    Length: 2.19 KB

Re: [Dynapi-Dev] Swiper Updates

[Daniel T. <de...@ti...>]

Hi!

The bug is fixed and aswell an unreported bug that made the layer "flicker" when used a function several times. This is made by adding a variable to the dynlayer witch is called "swiperMinimized" to keep the state of the swiper first time the swiper is used for the specific layer.

Regards
Daniel

> Hi,
> 
> The attached file is an update to the swiper library
> 
> I've renamed the inc-dec swipe values to inc-left,
> dec-right, etc in order to be consistent with
> top-right, bottom-left, etc
> 
> Bugs:
> 
> 1) If you were to press the dec-up or inc-left button
> more than once the layer would scroll off the screen
> 
> 2) The getClip() function now returns the correct
> values in opera v7 but there seems to be a bug with
> it's css clip property. Is there a workaround? Is this
> a known bug in opera?
> 
> 
> --
> Raymond Irving
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> ----------------------------------------------------
>      Name: swiper.zip
>      Type: application/x-zip-compressed
>  Encoding: base64
>    Length: 5.63 KB

RE: [Dynapi-Dev] HTMLMenus with sound effects

[Tobias J. <tob...@we...>]

Hi Raymond,

I get an error message: FlashSound undefined.
On system Win98, IE5.
Seems like FlashSound is internally not included the way it should be.

Regards,
Tobias

Part of your sourcecode:
---------------------------------
<script language="Javascript">
dynapi.library.setPath('../src/');
dynapi.library.include('dynapi.api');
dynapi.library.include('TemplateManager');
dynapi.library.include('HTMLMenu');
dynapi.library.include('FlashSound');

</script>
<script language="Javascript">

// Create and load flash sound file
ERROR--> fs = new FlashSound();
fs.setSWF("images/sndfx.swf");
HTMLComponent.setFlashSound(fs); // Set FlashSound object for all HCs
----------------------------------



-----Ursprüngliche Nachricht-----
Von: dyn...@li...
[mailto:dyn...@li...]Im Auftrag von Raymond
Irving
Gesendet: Montag, 30. Juni 2003 18:18
An: DynAPI-Dev; DynApi-Help
Betreff: [Dynapi-Dev] HTMLMenus with sound effects


Hello Everyone

Take a look at a online version of the  HTMLMenu with
sound effects. Use either IE or opera because they
have built-in support for the Flash Player

http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlmenu.html

The new sound events can be used in any DynAPI app to
create audible messages and warnings such as "Access
denied," etc

--
Raymond Irving

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://www.mail-archive.com/dyn...@li.../

[Dynapi-Dev] Swiper Updates

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

Hi,

The attached file is an update to the swiper library

I've renamed the inc-dec swipe values to inc-left,
dec-right, etc in order to be consistent with
top-right, bottom-left, etc

Bugs:

1) If you were to press the dec-up or inc-left button
more than once the layer would scroll off the screen

2) The getClip() function now returns the correct
values in opera v7 but there seems to be a bug with
it's css clip property. Is there a workaround? Is this
a known bug in opera?


--
Raymond Irving


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] [ dynapi-Bugs-763790 ] _destroy()

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

Bugs item #763790, was opened at 2003-07-01 12:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763790&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Tiru (tiru)
Assigned to: Nobody/Anonymous (nobody)
Summary: _destroy()

Initial Comment:
Hi!

When using destroy() on a dynlayer and reloading the 
page in ie i get this message:

line: 72
error: 'this.children.length' is null or not an object

After that it works fine again, no visible errors i mean, 
just that popup.

regards
Daniel

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763790&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-763598 ] DynAPI3 - IE Mac 5.2 Crashes when Refresh is clicked

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

Bugs item #763598, was opened at 2003-06-30 19:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763598&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Timothy Ace (ecammit)
Assigned to: Nobody/Anonymous (nobody)
Summary: DynAPI3 - IE Mac 5.2 Crashes when Refresh is clicked

Initial Comment:
This can be seen most prevailently in:

dynapi3x/tshoot/drag_forms.html

The page loads fine, but it crashes the whole browser
when you press the 'Refresh' Button.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763598&group_id=5757

[Dynapi-Dev] HTMLMenus with sound effects

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

Hello Everyone

Take a look at a online version of the  HTMLMenu with
sound effects. Use either IE or opera because they
have built-in support for the Flash Player

http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlmenu.html

The new sound events can be used in any DynAPI app to
create audible messages and warnings such as "Access
denied," etc

--
Raymond Irving

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] [ dynapi-Bugs-763285 ] HC List

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

Bugs item #763285, was opened at 2003-06-30 16:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763285&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Tiru (tiru)
Assigned to: Nobody/Anonymous (nobody)
Summary: HC List

Initial Comment:
Hi!

When using sort on the listboxes in opera it down work.

In the melon example all items in the list get changed to 
beeing melons.

Regards
Daniel

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763285&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-763279 ] Opera set/get Clip

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

Bugs item #763279, was opened at 2003-06-30 16:42
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763279&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Tiru (tiru)
Assigned to: Nobody/Anonymous (nobody)
Summary: Opera set/get Clip

Initial Comment:
The getClip in opera dont work wery well.
and aswell the setClip dont work.

You can check the swiper example to see what i mean.
I am using opera build 2887 (7.11).

The return values of getClip() is (123,NaN,NaN,NaN)
So the first one works if i am correct. 123 is just a 
dummy number but i hope you get my point.

Regards
Daniel Tiru

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=763279&group_id=5757

Re: [Dynapi-Dev] TemplateManager problem

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

This has been fixed.

The problem was with line 84:

if(oc && oc.removeFromParent) oc.removeFromParent; //
remove old child

change it to:

if(oc && oc.removeFromParent) oc.removeFromParent();
// remove old child


This example should now work:

var t= 'some text {@fld1} some text'
var tp = new Template(t,100,100,350,130,'#EEEEEE');
tp.addChild(new DynLayer('Test'),'fld1');

dynapi.onLoad(function(){
	tp.addChild(new DynLayer('First'),'fld1');
	tp.generate(); // very important!
});

dynapi.document.addChild(tp);

--
Raymond Irving


--- Daniel Tiru <de...@ti...> wrote:
> Hi!
> 
> I found today that in a template its not working to
> replace fields with another part.
> 
> I mean, say i have a template with one field
> then i add a layer to that field. So far no problem.
> 
> But when i try to add another layer nothing happens.
> I think this is some bug in the addChild method in
> the templatemanager but i am not sure.
> 
> Regards
> Daniel Tiru
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

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

Bugs item #762495, was opened at 2003-06-28 20:31
Message generated for change (Settings changed) made by xwisdom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Category: DynAPI 3 API
Group: Unverified
Status: Open
>Resolution: Fixed
Priority: 5
Submitted By: Sam Blum (bs_php)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong position retured when page has been scrolled down.

Initial Comment:
Reproduced the bug in IE and Mozilla 1.3

To see the effect, open the dynapi example:
examples/dynapi.api.mouseevent.html 
- You should see some colored layers that are cascaded 
in each 
  other in the middle of the page. 
- On the left we have some links to turn mouse-events 
on and off.
- The debugger window should open as well.

The page contains so much info, that a standard scroll-
bar should appear on the right of the browser. If not 
make the browser window less high.

Now do as follows:
A) Turn on the click/dblclick events for the blue layer. 
   This is done by clicking on the 
      "Listen to click/dblclick events -> blue -> on" 
   link (see the page)

B) Then click on the blue layer top left corner and look 
   at the output on the debugger window. It should say 
   something like this: 
   "click blue xy=0,0 pXY=300,200 origin=blue"

   NOTE: 
   xy are the coordinates of the click on the blue layer 
   relative to it's own top left corner. pXY are the 
   absolute coordinates relative to the view (top left 
   corner of the browser).

C) Now scroll down a little and click again on the blue 
   layer (try to hit the same spot). Now in the debugger 
   window look at the result: 
   "click blue xy=0,-148 pXY=300,52 origin=blue"

BUG: 
  Compare the xy result 0,0 and 0,-148. I would have 
  expected to get the same result in case A) and B) 
  for xy (the pXY results are OK). But the y axis has 
  a negative number, caused by the scrolling.
  
  
Side Effect Bug:  
  Next I modified the code and set the red layer 
to 'relative'
  Thus, I added line:  red.setPosition('relative');
  This will position the layers at the bottom of the 
  page. Again try to repeat B) and C) (as good as you 
can) 
  and compare the results:
    "click blue xy=8,496 pXY=308,696 origin=blue"
    "click blue xy=8,396 pXY=308,596 origin=blue"

The effect is the same AND a *side effect* shows up:
alway have an x offset of 8px (13px on IE). But I heard 
that reletive posistioning is problematic.

-- bs_php

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-06-30 12:55

Message:
Logged In: YES 
user_id=696242

Hi bs_php,

Bug verified and fixed

I've implemented your fix into the MouseEvent files and it 
seems to have resolve the porblem. Many thanks for this fix.

--
Raymond Irving

----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-28 23:18

Message:
Logged In: YES 
user_id=308859

This would my suggestion for mouse_dom.js

p.getScrollX = function() {return 
document.body.scrollTop||0};
p.getScrollY = function() {return 
document.body.scrollLeft||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};


This would my suggestion for mouse_ie.js
p.getScrollX = function() {return window.pageXOffset||0};
p.getScrollY = function() {return window.pageYOffset||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};



----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-28 22:47

Message:
Logged In: YES 
user_id=308859

OK here is the solution ( I know it' currently a hack) 
=================================
For Mozzila 1.3 in mouse_dom.js replace the lines:

  p.getX = function() {return this.x};
  p.getY = function() {return this.y};

with 

  p.getX_ = function() {
    var _x = this.x||0;
    var _xOffset = 0;
    if (this.ns) {
      _xOffset = document.body.scrollTop||0;
    }else{
      _xOffset = window.pageXOffset||0;
    }
    return _x + _xOffset;
  };
  
  p.getY_ = function() {
    var _y = this.y||0;
    var _yOffset = 0;
    if (this.ns) {
      _yOffset = document.body.scrollLeft||0;
    }else{
      _yOffset = window.pageYOffset||0;
    }
    return _y + _yOffset;
  };


NOTE: I've seen in the code that this.x and this.y are refered 
often directly (not using the getX()-methode) so there may 
more to correct then just the methods  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

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

Bugs item #762495, was opened at 2003-06-28 20:31
Message generated for change (Comment added) made by xwisdom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Category: DynAPI 3 API
Group: Unverified
Status: Open
Resolution: None
Priority: 5
Submitted By: Sam Blum (bs_php)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong position retured when page has been scrolled down.

Initial Comment:
Reproduced the bug in IE and Mozilla 1.3

To see the effect, open the dynapi example:
examples/dynapi.api.mouseevent.html 
- You should see some colored layers that are cascaded 
in each 
  other in the middle of the page. 
- On the left we have some links to turn mouse-events 
on and off.
- The debugger window should open as well.

The page contains so much info, that a standard scroll-
bar should appear on the right of the browser. If not 
make the browser window less high.

Now do as follows:
A) Turn on the click/dblclick events for the blue layer. 
   This is done by clicking on the 
      "Listen to click/dblclick events -> blue -> on" 
   link (see the page)

B) Then click on the blue layer top left corner and look 
   at the output on the debugger window. It should say 
   something like this: 
   "click blue xy=0,0 pXY=300,200 origin=blue"

   NOTE: 
   xy are the coordinates of the click on the blue layer 
   relative to it's own top left corner. pXY are the 
   absolute coordinates relative to the view (top left 
   corner of the browser).

C) Now scroll down a little and click again on the blue 
   layer (try to hit the same spot). Now in the debugger 
   window look at the result: 
   "click blue xy=0,-148 pXY=300,52 origin=blue"

BUG: 
  Compare the xy result 0,0 and 0,-148. I would have 
  expected to get the same result in case A) and B) 
  for xy (the pXY results are OK). But the y axis has 
  a negative number, caused by the scrolling.
  
  
Side Effect Bug:  
  Next I modified the code and set the red layer 
to 'relative'
  Thus, I added line:  red.setPosition('relative');
  This will position the layers at the bottom of the 
  page. Again try to repeat B) and C) (as good as you 
can) 
  and compare the results:
    "click blue xy=8,496 pXY=308,696 origin=blue"
    "click blue xy=8,396 pXY=308,596 origin=blue"

The effect is the same AND a *side effect* shows up:
alway have an x offset of 8px (13px on IE). But I heard 
that reletive posistioning is problematic.

-- bs_php

----------------------------------------------------------------------

>Comment By: Raymond Irving (xwisdom)
Date: 2003-06-30 12:55

Message:
Logged In: YES 
user_id=696242

Hi bs_php,

Bug verified and fixed

I've implemented your fix into the MouseEvent files and it 
seems to have resolve the porblem. Many thanks for this fix.

--
Raymond Irving

----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-28 23:18

Message:
Logged In: YES 
user_id=308859

This would my suggestion for mouse_dom.js

p.getScrollX = function() {return 
document.body.scrollTop||0};
p.getScrollY = function() {return 
document.body.scrollLeft||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};


This would my suggestion for mouse_ie.js
p.getScrollX = function() {return window.pageXOffset||0};
p.getScrollY = function() {return window.pageYOffset||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};



----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-28 22:47

Message:
Logged In: YES 
user_id=308859

OK here is the solution ( I know it' currently a hack) 
=================================
For Mozzila 1.3 in mouse_dom.js replace the lines:

  p.getX = function() {return this.x};
  p.getY = function() {return this.y};

with 

  p.getX_ = function() {
    var _x = this.x||0;
    var _xOffset = 0;
    if (this.ns) {
      _xOffset = document.body.scrollTop||0;
    }else{
      _xOffset = window.pageXOffset||0;
    }
    return _x + _xOffset;
  };
  
  p.getY_ = function() {
    var _y = this.y||0;
    var _yOffset = 0;
    if (this.ns) {
      _yOffset = document.body.scrollLeft||0;
    }else{
      _yOffset = window.pageYOffset||0;
    }
    return _y + _yOffset;
  };


NOTE: I've seen in the code that this.x and this.y are refered 
often directly (not using the getX()-methode) so there may 
more to correct then just the methods  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-759703 ] Library Error: could not find [TemplateManager]

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

Bugs item #759703, was opened at 2003-06-24 08:51
Message generated for change (Settings changed) made by xwisdom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=759703&group_id=5757

Category: None
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Submitted By: ben smith (b0nj0m0n)
Assigned to: Nobody/Anonymous (nobody)
Summary: Library Error: could not find [TemplateManager]

Initial Comment:
The library claims that it can't find TemplateManager or 
SnapX. I checked in /ext/packages.js, and the filenames 
listed there correspond with the correct physical 
filenames.  Using DynAPI 3.0.0 with Internet Explorer 6 
and Mozilla 1.4 on a RedHat/Apache server.  

http://benchmark.s-m-i-t-h.com/testNavBar.htm

I'm brand new to the water, but it looked cold, so I tried 
the diving board.  Thanks much - it looks great, wish I 
could get it to work.



----------------------------------------------------------------------

Comment By: ben smith (b0nj0m0n)
Date: 2003-06-26 05:06

Message:
Logged In: YES 
user_id=808185

XWisdom:

Thanks for new syntax reminder.

  I'm having trouble with CVSing DynAPI snapshots, it doesn't 
like my password when I enter it.  I don't want to waste this 
account but I'd much rather participate in new code than use 
old stable code - especially because I love the new features -
 and I'm on a time budget.  Has anyone had problems logging 
in?

Thanks!

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-06-24 13:12

Message:
Logged In: YES 
user_id=696242

Hi Ben,

Welcome to the new world of DynAPI 3.0

Thanks for the information. This issue has been resolved and 
will be in cvs soon.

On looking at your test page I found out that your still using 
the moveTo(x,y) function. This function was replaced with 
the setLocation(x,y) function

Enjoy!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=759703&group_id=5757

Re:[Dynapi-Dev] Documentation Stratagy for DynApi; is there one? ?

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

--- Leif W <war...@us...> wrote:
> Hey,
> 
> This thought just occured to me since I'm working on
> the server side stuff at
> the moment.  What about the documentation there? 
> For example, the client side
> docs for IOElement look pretty complete, but there's
> no server-side docs, just
> source code with sparse documentation.  But in the
> dialogue about
> documentation generation -- the server-side is going
> to have various languages
> (PHP, Perl, ASP, TCL, etc.) -- what's the plan for
> having docs generated for
> these additional languages?

Well I guess we might hav to use separate docs. Not
sure what's out there for multi-platform systems.
 
> Another thought that occured to me earlier.  It
> would be cool to have some
> sort of front end program (written in DynAPI?) that
> collected together things
> such as documentation generation, source
> compression, etc.
> 
> Looking for doc volunteers?  

Yes I think we need some more persons to start working
on the docs. Maybe we could start recruiting new
developers and document writers? If so please help to
spread the word around or we could launch an
advertising campaign :)


--
Raymond Irving


>I'm not too familiar
> with anything but the SnapX
> since that's all I wrote, but if it can be of help,
> tell me the format of
> comments and I can take care of that.  Otherwise,
> there's some comments in
> there already, maybe just needs some reformatting. 
> If there's any questions
> feel free to ask.  If it's just a matter of data
> entry or grunt work, I could
> help out if descriptions are provided to me, so I
> could go in and drop
> comments in place in proper format.
> 
> Leif
> 
> P.S. I go on vacation from July 3rd to 9th, so I'll
> not be around then.
> 
> 
> Raymond Irving <xw...@ya...> wrote:
> > 
> > --- Dan Willemsen <da...@wi...> wrote:
> > > 
> > > Quoting Darin Kadrioski
> > > <DKa...@lm...>:
> > > 
> > > > http://sourceforge.net/projects/jsdoc/
> > > 
> > > nice... the only question i have is whether it
> will
> > > parse some of the javascript
> > > that we use in dynapi, some of it isn't all so
> > > well-formed according to it's
> > > definition i don't think
> > 
> > "...With the exception of the rules stated above
> how
> > you document your code is not a matter of concern
> to
> > the parser...."
> > 
> > As long and the comments follow the jsDoc rules
> then
> > the DynAPI files will work great!
> > 
> > I think this a good start for the source codre
> > documentation.
> > 
> > The question now is who are the persons that will
> be
> > working on the source code documentation?  Dan I
> guess
> > your in on this one?
> > 
> > 
> > --
> > Raymond.
> > 
> > > --
> > > Dan Willemsen
> > > 
> > > 
> > > 
> > >
> >
>
-------------------------------------------------------
> > > This SF.Net email sponsored by: Free pre-built
> > > ASP.NET sites including
> > > Data Reports, E-commerce, Portals, and Forums
> are
> > > available now.
> > > Download today and enter to win an XBOX or
> Visual
> > > Studio .NET.
> > >
> >
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > >
> >
>
http://www.mail-archive.com/dyn...@li.../
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > SBC Yahoo! DSL - Now only $29.95 per month!
> > http://sbc.yahoo.com
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are
> available now.
> > Download today and enter to win an XBOX or Visual
> Studio .NET.
> >
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
>
http://www.mail-archive.com/dyn...@li.../
> > 
> 
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Dynapi-Dev] TemplateManager problem

[Daniel T. <de...@ti...>]

Hi!

I found today that in a template its not working to replace fields with another part.

I mean, say i have a template with one field
then i add a layer to that field. So far no problem.

But when i try to add another layer nothing happens. I think this is some bug in the addChild method in the templatemanager but i am not sure.

Regards
Daniel Tiru

[Dynapi-Dev] modified Swiper

[Daniel T. <de...@ti...>]

Hi!

I have now made the Swiper implementing the incdec functions and aswell modified the example so you can see how it works. Please report any bugs/features or if something needs to be changed cause of bad code or something... Its my first subbmission so :)

Best Regards
Daniel Tiru

[Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

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

Bugs item #762495, was opened at 2003-06-28 22:31
Message generated for change (Comment added) made by bs_php
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Category: DynAPI 3 API
Group: Unverified
Status: Open
Resolution: None
Priority: 5
Submitted By: Sam Blum (bs_php)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong position retured when page has been scrolled down.

Initial Comment:
Reproduced the bug in IE and Mozilla 1.3

To see the effect, open the dynapi example:
examples/dynapi.api.mouseevent.html 
- You should see some colored layers that are cascaded 
in each 
  other in the middle of the page. 
- On the left we have some links to turn mouse-events 
on and off.
- The debugger window should open as well.

The page contains so much info, that a standard scroll-
bar should appear on the right of the browser. If not 
make the browser window less high.

Now do as follows:
A) Turn on the click/dblclick events for the blue layer. 
   This is done by clicking on the 
      "Listen to click/dblclick events -> blue -> on" 
   link (see the page)

B) Then click on the blue layer top left corner and look 
   at the output on the debugger window. It should say 
   something like this: 
   "click blue xy=0,0 pXY=300,200 origin=blue"

   NOTE: 
   xy are the coordinates of the click on the blue layer 
   relative to it's own top left corner. pXY are the 
   absolute coordinates relative to the view (top left 
   corner of the browser).

C) Now scroll down a little and click again on the blue 
   layer (try to hit the same spot). Now in the debugger 
   window look at the result: 
   "click blue xy=0,-148 pXY=300,52 origin=blue"

BUG: 
  Compare the xy result 0,0 and 0,-148. I would have 
  expected to get the same result in case A) and B) 
  for xy (the pXY results are OK). But the y axis has 
  a negative number, caused by the scrolling.
  
  
Side Effect Bug:  
  Next I modified the code and set the red layer 
to 'relative'
  Thus, I added line:  red.setPosition('relative');
  This will position the layers at the bottom of the 
  page. Again try to repeat B) and C) (as good as you 
can) 
  and compare the results:
    "click blue xy=8,496 pXY=308,696 origin=blue"
    "click blue xy=8,396 pXY=308,596 origin=blue"

The effect is the same AND a *side effect* shows up:
alway have an x offset of 8px (13px on IE). But I heard 
that reletive posistioning is problematic.

-- bs_php

----------------------------------------------------------------------

>Comment By: Sam Blum (bs_php)
Date: 2003-06-29 01:18

Message:
Logged In: YES 
user_id=308859

This would my suggestion for mouse_dom.js

p.getScrollX = function() {return 
document.body.scrollTop||0};
p.getScrollY = function() {return 
document.body.scrollLeft||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};


This would my suggestion for mouse_ie.js
p.getScrollX = function() {return window.pageXOffset||0};
p.getScrollY = function() {return window.pageYOffset||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};



----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-29 00:47

Message:
Logged In: YES 
user_id=308859

OK here is the solution ( I know it' currently a hack) 
=================================
For Mozzila 1.3 in mouse_dom.js replace the lines:

  p.getX = function() {return this.x};
  p.getY = function() {return this.y};

with 

  p.getX_ = function() {
    var _x = this.x||0;
    var _xOffset = 0;
    if (this.ns) {
      _xOffset = document.body.scrollTop||0;
    }else{
      _xOffset = window.pageXOffset||0;
    }
    return _x + _xOffset;
  };
  
  p.getY_ = function() {
    var _y = this.y||0;
    var _yOffset = 0;
    if (this.ns) {
      _yOffset = document.body.scrollLeft||0;
    }else{
      _yOffset = window.pageYOffset||0;
    }
    return _y + _yOffset;
  };


NOTE: I've seen in the code that this.x and this.y are refered 
often directly (not using the getX()-methode) so there may 
more to correct then just the methods  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

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

Bugs item #762495, was opened at 2003-06-28 22:31
Message generated for change (Comment added) made by bs_php
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Category: DynAPI 3 API
Group: Unverified
Status: Open
Resolution: None
Priority: 5
Submitted By: Sam Blum (bs_php)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong position retured when page has been scrolled down.

Initial Comment:
Reproduced the bug in IE and Mozilla 1.3

To see the effect, open the dynapi example:
examples/dynapi.api.mouseevent.html 
- You should see some colored layers that are cascaded 
in each 
  other in the middle of the page. 
- On the left we have some links to turn mouse-events 
on and off.
- The debugger window should open as well.

The page contains so much info, that a standard scroll-
bar should appear on the right of the browser. If not 
make the browser window less high.

Now do as follows:
A) Turn on the click/dblclick events for the blue layer. 
   This is done by clicking on the 
      "Listen to click/dblclick events -> blue -> on" 
   link (see the page)

B) Then click on the blue layer top left corner and look 
   at the output on the debugger window. It should say 
   something like this: 
   "click blue xy=0,0 pXY=300,200 origin=blue"

   NOTE: 
   xy are the coordinates of the click on the blue layer 
   relative to it's own top left corner. pXY are the 
   absolute coordinates relative to the view (top left 
   corner of the browser).

C) Now scroll down a little and click again on the blue 
   layer (try to hit the same spot). Now in the debugger 
   window look at the result: 
   "click blue xy=0,-148 pXY=300,52 origin=blue"

BUG: 
  Compare the xy result 0,0 and 0,-148. I would have 
  expected to get the same result in case A) and B) 
  for xy (the pXY results are OK). But the y axis has 
  a negative number, caused by the scrolling.
  
  
Side Effect Bug:  
  Next I modified the code and set the red layer 
to 'relative'
  Thus, I added line:  red.setPosition('relative');
  This will position the layers at the bottom of the 
  page. Again try to repeat B) and C) (as good as you 
can) 
  and compare the results:
    "click blue xy=8,496 pXY=308,696 origin=blue"
    "click blue xy=8,396 pXY=308,596 origin=blue"

The effect is the same AND a *side effect* shows up:
alway have an x offset of 8px (13px on IE). But I heard 
that reletive posistioning is problematic.

-- bs_php

----------------------------------------------------------------------

>Comment By: Sam Blum (bs_php)
Date: 2003-06-29 00:47

Message:
Logged In: YES 
user_id=308859

OK here is the solution ( I know it' currently a hack) 
=================================
For Mozzila 1.3 in mouse_dom.js replace the lines:

  p.getX = function() {return this.x};
  p.getY = function() {return this.y};

with 

  p.getX_ = function() {
    var _x = this.x||0;
    var _xOffset = 0;
    if (this.ns) {
      _xOffset = document.body.scrollTop||0;
    }else{
      _xOffset = window.pageXOffset||0;
    }
    return _x + _xOffset;
  };
  
  p.getY_ = function() {
    var _y = this.y||0;
    var _yOffset = 0;
    if (this.ns) {
      _yOffset = document.body.scrollLeft||0;
    }else{
      _yOffset = window.pageYOffset||0;
    }
    return _y + _yOffset;
  };


NOTE: I've seen in the code that this.x and this.y are refered 
often directly (not using the getX()-methode) so there may 
more to correct then just the methods  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757