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

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

I always use the production version downloadable from the front page as tis is
what any client will be evaluating.

Ug.. more bugs you say? I've been working in vbscript and VB and sql for so
long that i think it will be a nice break to dive into some js again.

I am working 9-5, however, I will put asside an hour or so of my gaming time
in the evenings to test and bughunt.

I would like to get the current cvs packed up and delivered as the current
production version on the front page soonest, like say, Aug 7th? (for some
reason i've started hating deadlines far less than I used to..)

To the lurkers: Please let us know you are out there.. even if you do not have
time to help with the current beta push, It would make me feel better knowing
that you guys ares till out there to help if we get in a bad bind with a
particular bug :-)

cheers



Andrew Gillett <an...@ph...> said:

> I think that a beta2 release would be an excellent move.
> 
> Doug, I didn't realize that you where using beta1. I thought that since 
> it was fixed in CVS that was all that mattered. Sorry.
> 
> The beta1 examples are online at 
>
http://dynapi.sourceforge.net/releases/dynapi-3.0.0-beta1/docs/docs/examples.html.

> Could you take a look and see if any of them cause the problem?  I've 
> gone through a number of them with IE6 but I haven't been able to 
> generate that particular error.  I did see quite a few other errors 
> though. :-(
> 
> 
> Andrew.
> 
> 
> Leif W wrote:
> 
> >> <do...@cr...>
> >> 2005 July 22 Friday 15:02
> >>
> >> dynapi.library.setPath('/dynapi/');
> >> dynapi.library.include('dynapi.library');
> >> dynapi.library.include('dynapi.api');
> >>
> >> That's it that's all.. you don't even have to instantiate any layers.
> >>
> >> just move the mouse around a bunch fast, slow, medium whatever and 
> >> you will
> >> get the error. The only common denominator is that the mouse has to 
> >> be moving
> >> to produce the error.
> >
> >
> >
> > Ahh, ok, I was looking at the CVS version, and it really is fixed.
> >
> > In the production, you can even omit the 'dynapi.library' include.
> > All it takes is the 'dynapi.api' include to reproduce.
> >
> >>> > <do...@cr...>
> >>> > 2005 July 22 Friday 09:52
> >>> >
> >>> > Hrm.. well the bug still exists in the production code.
> >>> > This is not a small bug either, as it very consistant in producing
> >>> > said error
> >>> > on ie 6 no matter what you are coding.
> >>> >
> >>> > Can we publish a new production version then? maybe we can do a > 
> >>> small
> >>> > push to
> >>> > varify the current cvs version for publishing?
> >>
> >
> > Yeah, please try the CVS.  Maybe we can make a beta2 release from 
> > current CVS and test that?  Would that be helpful?  I realize that any 
> > mention of CVS may deter some people from attempting to install CVS 
> > software and pull down a copy.  In Windows with TortoiseCVS it has 
> > been fairly painless for me.
> >
> > Anyways, there's still stuff that may be broken, but I personally 
> > don't know them all.  So if anyone has a bug that has sat in the 
> > database and isn't fixed in CVS or the bug report is still open, then 
> > please ping us again.  Even just a message to the dev list with the 
> > bug numbers and a note to check it is helpful.  There's so many old 
> > ones, it's hard to know what should get priority at this point.  One 
> > at a time we can close them and hopefully get back to a mostly-closed 
> > state and make a new production release.
> >
> > Leif
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://www.mail-archive.com/dyn...@li.../
> >
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> 



-- 

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

[Andrew G. <an...@ph...>]

I think that a beta2 release would be an excellent move.

Doug, I didn't realize that you where using beta1. I thought that since 
it was fixed in CVS that was all that mattered. Sorry.

The beta1 examples are online at 
http://dynapi.sourceforge.net/releases/dynapi-3.0.0-beta1/docs/docs/examples.html. 
Could you take a look and see if any of them cause the problem?  I've 
gone through a number of them with IE6 but I haven't been able to 
generate that particular error.  I did see quite a few other errors 
though. :-(


Andrew.


Leif W wrote:

>> <do...@cr...>
>> 2005 July 22 Friday 15:02
>>
>> dynapi.library.setPath('/dynapi/');
>> dynapi.library.include('dynapi.library');
>> dynapi.library.include('dynapi.api');
>>
>> That's it that's all.. you don't even have to instantiate any layers.
>>
>> just move the mouse around a bunch fast, slow, medium whatever and 
>> you will
>> get the error. The only common denominator is that the mouse has to 
>> be moving
>> to produce the error.
>
>
>
> Ahh, ok, I was looking at the CVS version, and it really is fixed.
>
> In the production, you can even omit the 'dynapi.library' include.
> All it takes is the 'dynapi.api' include to reproduce.
>
>>> > <do...@cr...>
>>> > 2005 July 22 Friday 09:52
>>> >
>>> > Hrm.. well the bug still exists in the production code.
>>> > This is not a small bug either, as it very consistant in producing
>>> > said error
>>> > on ie 6 no matter what you are coding.
>>> >
>>> > Can we publish a new production version then? maybe we can do a > 
>>> small
>>> > push to
>>> > varify the current cvs version for publishing?
>>
>
> Yeah, please try the CVS.  Maybe we can make a beta2 release from 
> current CVS and test that?  Would that be helpful?  I realize that any 
> mention of CVS may deter some people from attempting to install CVS 
> software and pull down a copy.  In Windows with TortoiseCVS it has 
> been fairly painless for me.
>
> Anyways, there's still stuff that may be broken, but I personally 
> don't know them all.  So if anyone has a bug that has sat in the 
> database and isn't fixed in CVS or the bug report is still open, then 
> please ping us again.  Even just a message to the dev list with the 
> bug numbers and a note to check it is helpful.  There's so many old 
> ones, it's hard to know what should get priority at this point.  One 
> at a time we can close them and hopefully get back to a mostly-closed 
> state and make a new production release.
>
> Leif
>
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

> <do...@cr...>
> 2005 July 22 Friday 15:02
>
> dynapi.library.setPath('/dynapi/');
> dynapi.library.include('dynapi.library');
> dynapi.library.include('dynapi.api');
>
> That's it that's all.. you don't even have to instantiate any layers.
>
> just move the mouse around a bunch fast, slow, medium whatever and you 
> will
> get the error. The only common denominator is that the mouse has to be 
> moving
> to produce the error.


Ahh, ok, I was looking at the CVS version, and it really is fixed.

In the production, you can even omit the 'dynapi.library' include.
All it takes is the 'dynapi.api' include to reproduce.

>> > <do...@cr...>
>> > 2005 July 22 Friday 09:52
>> >
>> > Hrm.. well the bug still exists in the production code.
>> > This is not a small bug either, as it very consistant in producing
>> > said error
>> > on ie 6 no matter what you are coding.
>> >
>> > Can we publish a new production version then? maybe we can do a 
>> > small
>> > push to
>> > varify the current cvs version for publishing?

Yeah, please try the CVS.  Maybe we can make a beta2 release from 
current CVS and test that?  Would that be helpful?  I realize that any 
mention of CVS may deter some people from attempting to install CVS 
software and pull down a copy.  In Windows with TortoiseCVS it has been 
fairly painless for me.

Anyways, there's still stuff that may be broken, but I personally don't 
know them all.  So if anyone has a bug that has sat in the database and 
isn't fixed in CVS or the bug report is still open, then please ping us 
again.  Even just a message to the dev list with the bug numbers and a 
note to check it is helpful.  There's so many old ones, it's hard to 
know what should get priority at this point.  One at a time we can close 
them and hopefully get back to a mostly-closed state and make a new 
production release.

Leif

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

dynapi.library.setPath('/dynapi/');
dynapi.library.include('dynapi.library');
dynapi.library.include('dynapi.api');

That's it that's all.. you don't even have to instantiate any layers.

just move the mouse around a bunch fast, slow, medium whatever and you will
get the error. The only common denominator is that the mouse has to be moving
to produce the error.


Leif W <war...@us...> said:

> > <do...@cr...>
> > 2005 July 22 Friday 09:52
> >
> > Hrm.. well the bug still exists in the production code.
> > This is not a small bug either, as it very consistant in producing 
> > said error
> > on ie 6 no matter what you are coding.
> >
> > Can we publish a new production version then? maybe we can do a small 
> > push to
> > varify the current cvs version for publishing?
> 
> Hi Doug,
> 
> I was planning to look at it with IE6 today.  I spent yesterday setting 
> up the new list, fiddling with the mailing list and trackers.
> 
> But, I'm unsure how to produce the bug?  Is it a specific library that 
> causes the problem?  I can of course load them all and comment out one 
> at a time, but it'd save time if I knew exactly what to load.  ;-) 
> Also, it really occurs just with "the" library loaded and zipping the 
> mouse arround quickly?  Do I need to test any other conditions?  DynAPI 
> documents, layers, event handlers or html forms and so on?
> 
> Leif
> 
> > Andrew Gillett <an...@ph...> said:
> >
> >> I've closed this bug. The patch was actually applied by Raymond quite 
> >> a
> >> long time ago.
> >> His CVS comment was:
> >>  revision 1.7
> >>  date: 2003/09/14 14:36:00;  author: xwisdom;  state: Exp;  lines: 
> >> +2 -3
> >>  Patch for dynapi.api.MouseEvent bug
> >>  submitted by Peter Romianowski updated by Raymond
> >>
> >> I guess there are probably other items in the bug list that should be
> >> closed.
> >>
> >> Thanks Doug for raising this one.
> >> If you find any more like this, please let us know :-)
> >>
> >>
> >> Andrew.
> >>
> >>
> >> SourceForge.net wrote:
> >>
> >> >Bugs item #840767, was opened at 2003-11-12 07:31
> >> >Message generated for change (Comment added) made by doug_melvin
> >> >You can respond by visiting:
> >>
>
>>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
> >> >
> >> >Please note that this message will contain a full copy of the 
> >> >comment thread,
> >> >including the initial issue submission, for this request,
> >> >not just the latest update.
> >> >Category: DynAPI 3 API
> >> >Group: None
> >> >Status: Open
> >> >Resolution: None
> >> >Priority: 5
> >> >Submitted By: David Haggard (dhaggard)
> >> >Assigned to: Nobody/Anonymous (nobody)
> >> >Summary: mouse_ie.js null error, with possible patch
> >> >
> >> >Initial Comment:
> >> >Background:
> >> >Two objects on page (among others, but these seem to
> >> >be the &quot;offenders.&quot;
> >> >1) A single DynLayer with a single assigned
> >> >eventListener for mouseover/mouseout, and using the
> >> >glideTo method. Used to scroll a navigation menu up and
> >> >down at top of page.
> >> >2) A form button, disabled by default, with a &quot;title&quot;
> >> >attribute set. No onmouseover trap defined for this
> >> >button.
> >> >
> >> >Symptom:
> >> >   On rapid mouseover over the button, javacript error in
> >> >line 71 of mouse_ie.js. &quot;null is not an object.&quot;
> >> >   Interesting that this only happened when the mouse
> >> >was moving quickly. Never happened with slow mouse
> >> >movement.
> >> >
> >> >Lines 70-74 in mouse_ie.js --
> >> >----------------------------------
> >> >if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
> >> >  if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for
> >> >#15 (ie only)
> >> >  //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
> >> >me.bubble=false;
> >> >  if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
> >> >me.bubble=false;
> >> >}
> >> >---------------------------------
> >> >
> >> >I eliminated the problem, with no affect on correct
> >> >functionality, by changing to this:
> >> >
> >> >Lines 70-76 in mouse_ie.js --
> >> >---------------------------------
> >> >if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
> >> >  if (src != null) { // error handler if src is null
> >> >    if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for
> >> >#15 (ie only)
> >> >    //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
> >> >me.bubble=false;
> >> >    if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
> >> >me.bubble=false;
> >> >  }
> >> >}
> >> >--------------------------------
> >> >
> >> >May not be the best fix, but it worked for this strange
> >> >error. I searched and searched, and never could find
> >> >WHY this error was occurring with a form button that is
> >> >in no way using the DynAPI.
> >> >
> >> >David Haggard
> >> >
> >> >----------------------------------------------------------------------
> >> >
> >> >Comment By: Doug Melvin (doug_melvin)
> >> >Date: 2005-07-21 10:49
> >> >
> >> >Message:
> >> >Logged In: YES
> >> >user_id=184788
> >> >
> >> >I was experiencing a bug in IE 6 where simply moving the
> >> >mouse around would random generate the above error in teh
> >> >same code.
> >> >
> >> >This error occurs even when the full extent of you code is
> >> >to load the libraries (I.E. no layers created, no event
> >> >handlers added.. just load the api and library)
> >> >
> >> >Adding the above mentions fix (checking for src!=null b4
> >> >doing stuff to src) fixes this and breaks nothing else as
> >> >far as i can tell.
> >> >
> >> >I tested in IE 6 with the mouse event and drag event examples
> >> >
> >> >Could someone please add this fix and post to the cvs.
> >> >
> >> >2 years is long enough for this one imho.
> >> >
> >> >cheers
> >> >
> >> >----------------------------------------------------------------------
> >> >
> >> >You can respond by visiting:
> >>
>
>>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
> >> >
> >> >
> >> >-------------------------------------------------------
> >> >SF.Net email is sponsored by: Discover Easy Linux Migration 
> >> >Strategies
> >> >from IBM. Find simple to follow Roadmaps, straightforward articles,
> >> >informative Webcasts and more! Get everything you need to get up to
> >> >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> >> >_______________________________________________
> >> >Dynapi-Dev mailing list
> >> >Dyn...@li...
> >> >http://www.mail-archive.com/dyn...@li.../
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> SF.Net email is sponsored by: Discover Easy Linux Migration 
> >> Strategies
> >> from IBM. Find simple to follow Roadmaps, straightforward articles,
> >> informative Webcasts and more! Get everything you need to get up to
> >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> >> _______________________________________________
> >> Dynapi-Dev mailing list
> >> Dyn...@li...
> >> http://www.mail-archive.com/dyn...@li.../
> >>
> >
> >
> >
> > -- 
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://www.mail-archive.com/dyn...@li.../
> >
> > 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> 



-- 

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

> <do...@cr...>
> 2005 July 22 Friday 09:52
>
> Hrm.. well the bug still exists in the production code.
> This is not a small bug either, as it very consistant in producing 
> said error
> on ie 6 no matter what you are coding.
>
> Can we publish a new production version then? maybe we can do a small 
> push to
> varify the current cvs version for publishing?

Hi Doug,

I was planning to look at it with IE6 today.  I spent yesterday setting 
up the new list, fiddling with the mailing list and trackers.

But, I'm unsure how to produce the bug?  Is it a specific library that 
causes the problem?  I can of course load them all and comment out one 
at a time, but it'd save time if I knew exactly what to load.  ;-) 
Also, it really occurs just with "the" library loaded and zipping the 
mouse arround quickly?  Do I need to test any other conditions?  DynAPI 
documents, layers, event handlers or html forms and so on?

Leif

> Andrew Gillett <an...@ph...> said:
>
>> I've closed this bug. The patch was actually applied by Raymond quite 
>> a
>> long time ago.
>> His CVS comment was:
>>  revision 1.7
>>  date: 2003/09/14 14:36:00;  author: xwisdom;  state: Exp;  lines: 
>> +2 -3
>>  Patch for dynapi.api.MouseEvent bug
>>  submitted by Peter Romianowski updated by Raymond
>>
>> I guess there are probably other items in the bug list that should be
>> closed.
>>
>> Thanks Doug for raising this one.
>> If you find any more like this, please let us know :-)
>>
>>
>> Andrew.
>>
>>
>> SourceForge.net wrote:
>>
>> >Bugs item #840767, was opened at 2003-11-12 07:31
>> >Message generated for change (Comment added) made by doug_melvin
>> >You can respond by visiting:
>>
>>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
>> >
>> >Please note that this message will contain a full copy of the 
>> >comment thread,
>> >including the initial issue submission, for this request,
>> >not just the latest update.
>> >Category: DynAPI 3 API
>> >Group: None
>> >Status: Open
>> >Resolution: None
>> >Priority: 5
>> >Submitted By: David Haggard (dhaggard)
>> >Assigned to: Nobody/Anonymous (nobody)
>> >Summary: mouse_ie.js null error, with possible patch
>> >
>> >Initial Comment:
>> >Background:
>> >Two objects on page (among others, but these seem to
>> >be the &quot;offenders.&quot;
>> >1) A single DynLayer with a single assigned
>> >eventListener for mouseover/mouseout, and using the
>> >glideTo method. Used to scroll a navigation menu up and
>> >down at top of page.
>> >2) A form button, disabled by default, with a &quot;title&quot;
>> >attribute set. No onmouseover trap defined for this
>> >button.
>> >
>> >Symptom:
>> >   On rapid mouseover over the button, javacript error in
>> >line 71 of mouse_ie.js. &quot;null is not an object.&quot;
>> >   Interesting that this only happened when the mouse
>> >was moving quickly. Never happened with slow mouse
>> >movement.
>> >
>> >Lines 70-74 in mouse_ie.js --
>> >----------------------------------
>> >if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
>> >  if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for
>> >#15 (ie only)
>> >  //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
>> >me.bubble=false;
>> >  if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
>> >me.bubble=false;
>> >}
>> >---------------------------------
>> >
>> >I eliminated the problem, with no affect on correct
>> >functionality, by changing to this:
>> >
>> >Lines 70-76 in mouse_ie.js --
>> >---------------------------------
>> >if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
>> >  if (src != null) { // error handler if src is null
>> >    if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for
>> >#15 (ie only)
>> >    //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
>> >me.bubble=false;
>> >    if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent)))
>> >me.bubble=false;
>> >  }
>> >}
>> >--------------------------------
>> >
>> >May not be the best fix, but it worked for this strange
>> >error. I searched and searched, and never could find
>> >WHY this error was occurring with a form button that is
>> >in no way using the DynAPI.
>> >
>> >David Haggard
>> >
>> >----------------------------------------------------------------------
>> >
>> >Comment By: Doug Melvin (doug_melvin)
>> >Date: 2005-07-21 10:49
>> >
>> >Message:
>> >Logged In: YES
>> >user_id=184788
>> >
>> >I was experiencing a bug in IE 6 where simply moving the
>> >mouse around would random generate the above error in teh
>> >same code.
>> >
>> >This error occurs even when the full extent of you code is
>> >to load the libraries (I.E. no layers created, no event
>> >handlers added.. just load the api and library)
>> >
>> >Adding the above mentions fix (checking for src!=null b4
>> >doing stuff to src) fixes this and breaks nothing else as
>> >far as i can tell.
>> >
>> >I tested in IE 6 with the mouse event and drag event examples
>> >
>> >Could someone please add this fix and post to the cvs.
>> >
>> >2 years is long enough for this one imho.
>> >
>> >cheers
>> >
>> >----------------------------------------------------------------------
>> >
>> >You can respond by visiting:
>>
>>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
>> >
>> >
>> >-------------------------------------------------------
>> >SF.Net email is sponsored by: Discover Easy Linux Migration 
>> >Strategies
>> >from IBM. Find simple to follow Roadmaps, straightforward articles,
>> >informative Webcasts and more! Get everything you need to get up to
>> >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> >_______________________________________________
>> >Dynapi-Dev mailing list
>> >Dyn...@li...
>> >http://www.mail-archive.com/dyn...@li.../
>> >
>> >
>> >
>>
>>
>>
>> -------------------------------------------------------
>> SF.Net email is sponsored by: Discover Easy Linux Migration 
>> Strategies
>> from IBM. Find simple to follow Roadmaps, straightforward articles,
>> informative Webcasts and more! Get everything you need to get up to
>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> _______________________________________________
>> Dynapi-Dev mailing list
>> Dyn...@li...
>> http://www.mail-archive.com/dyn...@li.../
>>
>
>
>
> -- 
>
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>
> 

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

Hrm.. well the bug still exists in the production code.
This is not a small bug either, as it very consistant in producing said error
on ie 6 no matter what you are coding.

Can we publish a new production version then? maybe we can do a small push to
varify the current cvs version for publishing?

Andrew Gillett <an...@ph...> said:

> I've closed this bug. The patch was actually applied by Raymond quite a 
> long time ago.
> His CVS comment was:
>  revision 1.7
>  date: 2003/09/14 14:36:00;  author: xwisdom;  state: Exp;  lines: +2 -3
>  Patch for dynapi.api.MouseEvent bug
>  submitted by Peter Romianowski updated by Raymond
> 
> I guess there are probably other items in the bug list that should be 
> closed.
> 
> Thanks Doug for raising this one.
> If you find any more like this, please let us know :-)
> 
> 
> Andrew.
> 
> 
> SourceForge.net wrote:
> 
> >Bugs item #840767, was opened at 2003-11-12 07:31
> >Message generated for change (Comment added) made by doug_melvin
> >You can respond by visiting: 
>
>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
> >
> >Please note that this message will contain a full copy of the comment thread,
> >including the initial issue submission, for this request,
> >not just the latest update.
> >Category: DynAPI 3 API
> >Group: None
> >Status: Open
> >Resolution: None
> >Priority: 5
> >Submitted By: David Haggard (dhaggard)
> >Assigned to: Nobody/Anonymous (nobody)
> >Summary: mouse_ie.js null error, with possible patch
> >
> >Initial Comment:
> >Background: 
> >Two objects on page (among others, but these seem to 
> >be the &quot;offenders.&quot;
> >1) A single DynLayer with a single assigned 
> >eventListener for mouseover/mouseout, and using the 
> >glideTo method. Used to scroll a navigation menu up and 
> >down at top of page. 
> >2) A form button, disabled by default, with a &quot;title&quot; 
> >attribute set. No onmouseover trap defined for this 
> >button.
> >
> >Symptom:
> >   On rapid mouseover over the button, javacript error in 
> >line 71 of mouse_ie.js. &quot;null is not an object.&quot;
> >   Interesting that this only happened when the mouse 
> >was moving quickly. Never happened with slow mouse 
> >movement.
> >
> >Lines 70-74 in mouse_ie.js --
> >----------------------------------
> >if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
> >  if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for 
> >#15 (ie only)
> >  //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
> >me.bubble=false;
> >  if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
> >me.bubble=false;
> >}
> >---------------------------------
> >
> >I eliminated the problem, with no affect on correct 
> >functionality, by changing to this:
> >
> >Lines 70-76 in mouse_ie.js --
> >---------------------------------
> >if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
> >  if (src != null) {	// error handler if src is null
> >    if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for 
> >#15 (ie only)
> >    //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
> >me.bubble=false;
> >    if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
> >me.bubble=false;
> >  }
> >}
> >--------------------------------
> >
> >May not be the best fix, but it worked for this strange 
> >error. I searched and searched, and never could find 
> >WHY this error was occurring with a form button that is 
> >in no way using the DynAPI.
> >
> >David Haggard
> >
> >----------------------------------------------------------------------
> >
> >Comment By: Doug Melvin (doug_melvin)
> >Date: 2005-07-21 10:49
> >
> >Message:
> >Logged In: YES 
> >user_id=184788
> >
> >I was experiencing a bug in IE 6 where simply moving the
> >mouse around would random generate the above error in teh
> >same code.
> >
> >This error occurs even when the full extent of you code is
> >to load the libraries (I.E. no layers created, no event
> >handlers added.. just load the api and library)
> >
> >Adding the above mentions fix (checking for src!=null b4
> >doing stuff to src) fixes this and breaks nothing else as
> >far as i can tell.
> >
> >I tested in IE 6 with the mouse event and drag event examples
> >
> >Could someone please add this fix and post to the cvs.
> >
> >2 years is long enough for this one imho.
> >
> >cheers
> >
> >----------------------------------------------------------------------
> >
> >You can respond by visiting: 
>
>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
> >
> >
> >-------------------------------------------------------
> >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> >from IBM. Find simple to follow Roadmaps, straightforward articles,
> >informative Webcasts and more! Get everything you need to get up to
> >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> >_______________________________________________
> >Dynapi-Dev mailing list
> >Dyn...@li...
> >http://www.mail-archive.com/dyn...@li.../
> >
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
> 



-- 

[Dynapi-Dev] New notification mailing list.

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

The new list is dynapi-notify.

Previously, all the tracker notifications have been dumped to 
dynapi-dev.  Well, we haven't had too many notifications lately, but 
looking through the mail archives, this can be confusing as it all adds 
up.  So I have created a new mailing list and have forwarded all tracker 
updates mail there.  This new list is not for posting messages or 
discussions.  It's to notify all who might be interested in any new 
tracker activity.  The discussions can be made on other lists like 
dynapi-dev, dynapi-help, dynapi-chat or dynapi-widgetdev.

To subscribe via the web:
https://lists.sourceforge.net/lists/listinfo/dynapi-notify

I modified the page and it may or may not work.
I'm sorry and too tired to fix right now.  :p
If that page is broken, try the email method.

To subscribe via email:

Send a message to dyn...@li... with 
"subscribe" as the subject (no quotes), and an empty message body.

Leif

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

Thanks Doug for pinging this.  If there are any other things you're 
wondering why no one responded to for 2-3 years, feel free to ping them 
too.  One at a time we can get them all.  Thanks for looking into this 
one too, Andrew.  You beat me to it.  :p  I too was looking at this.  I 
did pull a fresh CVS but did not look at the previous commit messages. 
I still want to test it just to make sure I understand it and verify 
that it's still fixed.

On a related note, since pushing this message through to the Dev list, I 
was thinking again.  Should I let all these tracker notifications flood 
the dev list or make a new list?  Well I decided to make a new list for 
that, so I have been setting up a list specifically to receive all the 
tracker messages from now on.  That should be read-only, whereas this 
dev list is where any subsequent discussions can take place.  I believe 
I mentioned something about this way back on the admin list, no replies. 
:p  Anyways it's how MinGW is doing it, and that seems to work well 
enough.

BTW: If anyone wants to ping in a real-time chat setting, pop on to IRC 
/server irc.freenode.net and /join #dynapi .  I leave myself idling in 
there.  Sometimes I am away and my system might crash (or someone else 
powers off), and I may or may not see a message in the logs when I next 
connect.  But generally I am on there and check the window a few times 
an hour.  If I disconnect without responding, there's the chance I miss 
a message, so you can leave a system message if it's critical.  So far 
no one but me has ever been there when I was there, so whoever is first 
will get a +v.  :p  Gaim is a nifty multi-IM (including IRC) and 
multi-OS client (including Linux & Windows), if you need a simple IRC 
client, otherwise mIRC is available for free usage in Windows.

Leif

----- Original Message ----- 
From: "Andrew Gillett" <an...@ph...>
To: <dyn...@li...>
Sent: 2005 July 22 Friday 00:13
Subject: Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, 
with possible patch


> I've closed this bug. The patch was actually applied by Raymond quite 
> a long time ago.
> His CVS comment was:
> revision 1.7
> date: 2003/09/14 14:36:00;  author: xwisdom;  state: Exp;  lines: 
> +2 -3
> Patch for dynapi.api.MouseEvent bug
> submitted by Peter Romianowski updated by Raymond
>
> I guess there are probably other items in the bug list that should be 
> closed.
>
> Thanks Doug for raising this one.
> If you find any more like this, please let us know :-)
>
>
> Andrew.
>
>
> SourceForge.net wrote:
>
>>Bugs item #840767, was opened at 2003-11-12 07:31
>>Message generated for change (Comment added) made by doug_melvin
>>You can respond by visiting: 
>>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
>>
>>Please note that this message will contain a full copy of the comment 
>>thread,
>>including the initial issue submission, for this request,
>>not just the latest update.
>>Category: DynAPI 3 API
>>Group: None
>>Status: Open
>>Resolution: None
>>Priority: 5
>>Submitted By: David Haggard (dhaggard)
>>Assigned to: Nobody/Anonymous (nobody)
>>Summary: mouse_ie.js null error, with possible patch
>>
>>Initial Comment:
>>Background: Two objects on page (among others, but these seem to be 
>>the &quot;offenders.&quot;
>>1) A single DynLayer with a single assigned eventListener for 
>>mouseover/mouseout, and using the glideTo method. Used to scroll a 
>>navigation menu up and down at top of page. 2) A form button, disabled 
>>by default, with a &quot;title&quot; attribute set. No onmouseover 
>>trap defined for this button.
>>
>>Symptom:
>>   On rapid mouseover over the button, javacript error in line 71 of 
>> mouse_ie.js. &quot;null is not an object.&quot;
>>   Interesting that this only happened when the mouse was moving 
>> quickly. Never happened with slow mouse movement.
>>
>>Lines 70-74 in mouse_ie.js --
>>----------------------------------
>>if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
>>  if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for #15 
>> (ie only)
>>  //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
>> me.bubble=false;
>>  if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
>> me.bubble=false;
>>}
>>---------------------------------
>>
>>I eliminated the problem, with no affect on correct functionality, by 
>>changing to this:
>>
>>Lines 70-76 in mouse_ie.js --
>>---------------------------------
>>if (e.type==&quot;mouseout&quot; || e.type==&quot;mouseover&quot;) {
>>  if (src != null) { // error handler if src is null
>>    if (r &amp;&amp; (r==src||src.isParentOf(r))) return; //fix for 
>> #15 (ie only)
>>    //if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
>> me.bubble=false;
>>    if (r&amp;&amp;(r==src.parent||r.isChildOf(src.parent))) 
>> me.bubble=false;
>>  }
>>}
>>--------------------------------
>>
>>May not be the best fix, but it worked for this strange error. I 
>>searched and searched, and never could find WHY this error was 
>>occurring with a form button that is in no way using the DynAPI.
>>
>>David Haggard
>>
>>----------------------------------------------------------------------
>>
>>Comment By: Doug Melvin (doug_melvin)
>>Date: 2005-07-21 10:49
>>
>>Message:
>>Logged In: YES user_id=184788
>>
>>I was experiencing a bug in IE 6 where simply moving the
>>mouse around would random generate the above error in teh
>>same code.
>>
>>This error occurs even when the full extent of you code is
>>to load the libraries (I.E. no layers created, no event
>>handlers added.. just load the api and library)
>>
>>Adding the above mentions fix (checking for src!=null b4
>>doing stuff to src) fixes this and breaks nothing else as
>>far as i can tell.
>>
>>I tested in IE 6 with the mouse event and drag event examples
>>
>>Could someone please add this fix and post to the cvs.
>>
>>2 years is long enough for this one imho.
>>
>>cheers
>>
>>----------------------------------------------------------------------
>>
>>You can respond by visiting: 
>>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>informative Webcasts and more! Get everything you need to get up to
>>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>_______________________________________________
>>Dynapi-Dev mailing list
>>Dyn...@li...
>>http://www.mail-archive.com/dyn...@li.../
>>
>>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>
> 

Re: [Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

[Andrew G. <an...@ph...>]

I've closed this bug. The patch was actually applied by Raymond quite a 
long time ago.
His CVS comment was:
 revision 1.7
 date: 2003/09/14 14:36:00;  author: xwisdom;  state: Exp;  lines: +2 -3
 Patch for dynapi.api.MouseEvent bug
 submitted by Peter Romianowski updated by Raymond

I guess there are probably other items in the bug list that should be 
closed.

Thanks Doug for raising this one.
If you find any more like this, please let us know :-)


Andrew.


SourceForge.net wrote:

>Bugs item #840767, was opened at 2003-11-12 07:31
>Message generated for change (Comment added) made by doug_melvin
>You can respond by visiting: 
>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
>
>Please note that this message will contain a full copy of the comment thread,
>including the initial issue submission, for this request,
>not just the latest update.
>Category: DynAPI 3 API
>Group: None
>Status: Open
>Resolution: None
>Priority: 5
>Submitted By: David Haggard (dhaggard)
>Assigned to: Nobody/Anonymous (nobody)
>Summary: mouse_ie.js null error, with possible patch
>
>Initial Comment:
>Background: 
>Two objects on page (among others, but these seem to 
>be the "offenders."
>1) A single DynLayer with a single assigned 
>eventListener for mouseover/mouseout, and using the 
>glideTo method. Used to scroll a navigation menu up and 
>down at top of page. 
>2) A form button, disabled by default, with a "title" 
>attribute set. No onmouseover trap defined for this 
>button.
>
>Symptom:
>   On rapid mouseover over the button, javacript error in 
>line 71 of mouse_ie.js. "null is not an object."
>   Interesting that this only happened when the mouse 
>was moving quickly. Never happened with slow mouse 
>movement.
>
>Lines 70-74 in mouse_ie.js --
>----------------------------------
>if (e.type=="mouseout" || e.type=="mouseover") {
>  if (r && (r==src||src.isParentOf(r))) return; //fix for 
>#15 (ie only)
>  //if (r&&(r==src.parent||r.isChildOf(src.parent))) 
>me.bubble=false;
>  if (r&&(r==src.parent||r.isChildOf(src.parent))) 
>me.bubble=false;
>}
>---------------------------------
>
>I eliminated the problem, with no affect on correct 
>functionality, by changing to this:
>
>Lines 70-76 in mouse_ie.js --
>---------------------------------
>if (e.type=="mouseout" || e.type=="mouseover") {
>  if (src != null) {	// error handler if src is null
>    if (r && (r==src||src.isParentOf(r))) return; //fix for 
>#15 (ie only)
>    //if (r&&(r==src.parent||r.isChildOf(src.parent))) 
>me.bubble=false;
>    if (r&&(r==src.parent||r.isChildOf(src.parent))) 
>me.bubble=false;
>  }
>}
>--------------------------------
>
>May not be the best fix, but it worked for this strange 
>error. I searched and searched, and never could find 
>WHY this error was occurring with a form button that is 
>in no way using the DynAPI.
>
>David Haggard
>
>----------------------------------------------------------------------
>
>Comment By: Doug Melvin (doug_melvin)
>Date: 2005-07-21 10:49
>
>Message:
>Logged In: YES 
>user_id=184788
>
>I was experiencing a bug in IE 6 where simply moving the
>mouse around would random generate the above error in teh
>same code.
>
>This error occurs even when the full extent of you code is
>to load the libraries (I.E. no layers created, no event
>handlers added.. just load the api and library)
>
>Adding the above mentions fix (checking for src!=null b4
>doing stuff to src) fixes this and breaks nothing else as
>far as i can tell.
>
>I tested in IE 6 with the mouse event and drag event examples
>
>Could someone please add this fix and post to the cvs.
>
>2 years is long enough for this one imho.
>
>cheers
>
>----------------------------------------------------------------------
>
>You can respond by visiting: 
>https://sourceforge.net/tracker/?func=detail&atid=105757&aid=840767&group_id=5757
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://www.mail-archive.com/dyn...@li.../
>
>  
>

[Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DynAPI 3 API
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: David Haggard (dhaggard)
Assigned to: Nobody/Anonymous (nobody)
Summary: mouse_ie.js null error, with possible patch

Initial Comment:
Background: 
Two objects on page (among others, but these seem to 
be the "offenders."
1) A single DynLayer with a single assigned 
eventListener for mouseover/mouseout, and using the 
glideTo method. Used to scroll a navigation menu up and 
down at top of page. 
2) A form button, disabled by default, with a "title" 
attribute set. No onmouseover trap defined for this 
button.

Symptom:
   On rapid mouseover over the button, javacript error in 
line 71 of mouse_ie.js. "null is not an object."
   Interesting that this only happened when the mouse 
was moving quickly. Never happened with slow mouse 
movement.

Lines 70-74 in mouse_ie.js --
----------------------------------
if (e.type=="mouseout" || e.type=="mouseover") {
  if (r && (r==src||src.isParentOf(r))) return; //fix for 
#15 (ie only)
  //if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
  if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
}
---------------------------------

I eliminated the problem, with no affect on correct 
functionality, by changing to this:

Lines 70-76 in mouse_ie.js --
---------------------------------
if (e.type=="mouseout" || e.type=="mouseover") {
  if (src != null) {	// error handler if src is null
    if (r && (r==src||src.isParentOf(r))) return; //fix for 
#15 (ie only)
    //if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
    if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
  }
}
--------------------------------

May not be the best fix, but it worked for this strange 
error. I searched and searched, and never could find 
WHY this error was occurring with a form button that is 
in no way using the DynAPI.

David Haggard

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

>Comment By: Andrew Gillett (agillett)
Date: 2005-07-22 12:46

Message:
Logged In: YES 
user_id=134108

This was fixed by raymond quite a while back.  His CVS comment:

revision 1.7
date: 2003/09/14 14:36:00;  author: xwisdom;  state: Exp; 
lines: +2 -3
Patch for dynapi.api.MouseEvent bug
submitted by Peter Romianowski updated by Raymond


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

Comment By: Andrew Gillett (agillett)
Date: 2005-07-22 12:46

Message:
Logged In: YES 
user_id=134108

The bug has been verified and a fix for the bug has been 
implemented.  The fix should be available in CVS as well as the 
next official release of the DynAPI.

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

Comment By: Doug Melvin (doug_melvin)
Date: 2005-07-22 03:49

Message:
Logged In: YES 
user_id=184788

I was experiencing a bug in IE 6 where simply moving the
mouse around would random generate the above error in teh
same code.

This error occurs even when the full extent of you code is
to load the libraries (I.E. no layers created, no event
handlers added.. just load the api and library)

Adding the above mentions fix (checking for src!=null b4
doing stuff to src) fixes this and breaks nothing else as
far as i can tell.

I tested in IE 6 with the mouse event and drag event examples

Could someone please add this fix and post to the cvs.

2 years is long enough for this one imho.

cheers

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

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

[Dynapi-Dev] [ dynapi-Bugs-840767 ] mouse_ie.js null error, with possible patch

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

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

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: David Haggard (dhaggard)
Assigned to: Nobody/Anonymous (nobody)
Summary: mouse_ie.js null error, with possible patch

Initial Comment:
Background: 
Two objects on page (among others, but these seem to 
be the "offenders."
1) A single DynLayer with a single assigned 
eventListener for mouseover/mouseout, and using the 
glideTo method. Used to scroll a navigation menu up and 
down at top of page. 
2) A form button, disabled by default, with a "title" 
attribute set. No onmouseover trap defined for this 
button.

Symptom:
   On rapid mouseover over the button, javacript error in 
line 71 of mouse_ie.js. "null is not an object."
   Interesting that this only happened when the mouse 
was moving quickly. Never happened with slow mouse 
movement.

Lines 70-74 in mouse_ie.js --
----------------------------------
if (e.type=="mouseout" || e.type=="mouseover") {
  if (r && (r==src||src.isParentOf(r))) return; //fix for 
#15 (ie only)
  //if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
  if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
}
---------------------------------

I eliminated the problem, with no affect on correct 
functionality, by changing to this:

Lines 70-76 in mouse_ie.js --
---------------------------------
if (e.type=="mouseout" || e.type=="mouseover") {
  if (src != null) {	// error handler if src is null
    if (r && (r==src||src.isParentOf(r))) return; //fix for 
#15 (ie only)
    //if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
    if (r&&(r==src.parent||r.isChildOf(src.parent))) 
me.bubble=false;
  }
}
--------------------------------

May not be the best fix, but it worked for this strange 
error. I searched and searched, and never could find 
WHY this error was occurring with a form button that is 
in no way using the DynAPI.

David Haggard

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

Comment By: Doug Melvin (doug_melvin)
Date: 2005-07-21 10:49

Message:
Logged In: YES 
user_id=184788

I was experiencing a bug in IE 6 where simply moving the
mouse around would random generate the above error in teh
same code.

This error occurs even when the full extent of you code is
to load the libraries (I.E. no layers created, no event
handlers added.. just load the api and library)

Adding the above mentions fix (checking for src!=null b4
doing stuff to src) fixes this and breaks nothing else as
far as i can tell.

I tested in IE 6 with the mouse event and drag event examples

Could someone please add this fix and post to the cvs.

2 years is long enough for this one imho.

cheers

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

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

[Dynapi-Dev] ThyAPI Released

[Vinicius C. B. <vin...@gm...>]

Hi developers:

There was talked some time ago in this list about ThyAPI, a library
based in DynAPI that implements a set of widgets. A release candidate
of this library was released in http://www.sf.net/projects/thyapi ,
and is available for downloading and testing.

We are organizing the documentation of the library each day. Its site
is http://thyapi.thyamad.com and there is a link there to the current
documentation.

Regards,

Vinicius

--------------------
Vinicius Cubas Brand
vin...@th...
--------------------
Thyamad Projects - http://www.thyamad.com
Turn Information into Productivity
Phone +55 41 30133867 - ICQ# 31027458=20
MSN vc...@ho...
--------------------
Concisus     - http://concis.us=20
ThyAPI       - http://thyapi.thyamad.com
eAccelerator - http://www.eaccelerator.net


------
Be the change you want to see in the world.
-- Mahatma Gandhi

[Dynapi-Dev] [ dynapi-Bugs-1232705 ] SQL bigint values lost in SODA object transit

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

Bugs item #1232705, was opened at 2005-07-05 08:02
Message generated for change (Comment added) made by warp9pnt9
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=1232705&group_id=5757

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DynAPI 3 API
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: conanDrum (conandrum)
Assigned to: L W (warp9pnt9)
Summary: SQL bigint values lost in SODA object transit

Initial Comment:
I believe the title says it all.
When you access an SQL database and retrieve a bigint 
value, then stick this into a dictionary object (VB ASP) 
and return the object to the client (JS HTML), the value 
on the client is recognised as [NULL].

If you return the value in a string all is well.

In General the behaviour is as follows:

Return value as:        Results in:
integer                 Overflow Error
array                   [NULL] value
object                  [NULL] value
string                  OK

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

>Comment By: L W (warp9pnt9)
Date: 2005-07-12 04:32

Message:
Logged In: YES 
user_id=706287

Well, Andrew set the record straight.

"According to the ECMAScript specification, numbers are
stored in IEEE 754 floating point format (52-bit fraction,
11-bit biased exponent, and a 1-bit sign). The language does
not support integers at all, so there is no chance of
representing a 64 bit integer. The number you got
(9007199254740992) is near enough to 2^53, which is about
what you should expect."

The JavaScript language itself does not support big
integers.  You'll have to use them as strings in the client,
and convert them to big integers on the server side, if the
server language supports them.

This bug is closed.

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

Comment By: L W (warp9pnt9)
Date: 2005-07-07 22:15

Message:
Logged In: YES 
user_id=706287

I've sent an email to the submitter's users.sourceforge.net
address and CCed to DynAPI-Dev mailing list.  No response
from the submitter.  Pasting the message here.  Subsequent
followup afterwards.

---- BEGIN COPY ----
Hi.  I'll try to help you with this so we can both better
understand what's going on.  Please be patient with me. 
It's been a while since I touched ASP, and currently do not
have a test platform.  At present I am only aware of
http://domaindlx.com/ with their free ASP hosting with
Microsoft Access via connectionless DN with ADODB.

If you provide a specific example of what you are trying to
do, what you are expecting, and what you are observing, then
I will be much closer to understanding the situation. 
Please do the following to help me:

1) Isolate the specific example of the code that causes the
problem.
2) Duplicate the error at DomainDLX.
3) Zip up the files and send to me with your commentary.

This will greatly help speed up the process.  Wether it's a
bug in the code, or in the documentation, or something else,
I am not sure so I can't rule anything out at this point.
---- END COPY ----

Upon some inspection of the relevant bits of code, it seems
perfectly normal that the data is sent back and forth as
text strings.  It was designed to do this.  So I have to
wonder about what is meant by "bigint".  Can you further
describe the "bigint" you refer to? Number of bits (or
min/max), signed or unsigned, and so on.

Take such a number in plain JavaScript on your client. 
Write it as a string, and then pass that string to
JavaScript's "parseInt".  I think it may be a limitation of
the browser's parseInt, or perhaps the client browser's
architechture doesn't support a "bigint", or the client
program wasn't compiled with support for "bigints".  I don't
think it has anything to do with SODA.  It's just in the
middle passing strings.  It relies on "parseInt", which
relies on the browser, which relies on the math library,
which may rely on the OS and CPU.

But to be completely sure, please test and report the
results.  I expect you'll confirm my guess.  Otherwise I'll
just close this and file it as "not a bug".  But if people
are going to be using this for bigints, I'll have to update
the documentation with this particular "gotcha".

Try to test the attached HTML + JavaScript file and use
trial and error to find the biggest number that you enter
(as a string), and can parse (as an int) and display (as a
string again), without losing digits.  The biggest/smallest
I can get is +/- hex 20 0000 0000 0000 or dec 9007199254740992.

Bottom line: you can only use ints that your client's
parseInt supports.  If you're not doing arithmetic
operations on the bigint, then just use it as a string.  If
you've got to do arithmetic operations, you've got to test
your browser capabilities and use only int sizes that are
supported.

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

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

Re: [Dynapi-Dev] Browser limitations of big integers.

[Andrew G. <an...@dy...>]

According to the ECMAScript specification, numbers are stored in IEEE 
754 floating point format (52-bit fraction, 11-bit biased exponent, and 
a 1-bit sign).
The language does not support integers at all, so there is no chance of 
representing a 64 bit integer.
The number you got (9007199254740992) is near enough to 2^53, which is 
about what you should expect.

Andrew


Leif W wrote:

> Hello,
>
> I don't know if anyone has followed the bug report for 1232705.  An 
> issue is raised about big integer support.  For the purposes of this 
> context, big integers shall be anything bigger than 32-bits, either 
> signed or unsigned, and may herein be expressed in either hex or 
> decimal (preferably both).
>
> The biggest/smallest integer I can get in Mozilla Firefox on WinXP 32 
> is +/- hex 20 0000 0000 0000 or dec 9007199254740992.  I have not 
> tested in Linux yet.  Can anyone on other OSes or browsers get bigger 
> or smaller numbers?  I wrote a simply JavaScript to help, and attached 
> it to the bug report.
>
> The JavaScript page merely has some buttons with predefined numbers, 
> an input field, a parse button, and an output field.  The "parse" 
> button takes the string representation in the input text field, passes 
> it to parseInt to make an integer.  Then it assigns that integer to 
> the value of the output text field, which implicitly converts back to 
> a string. The strings expect decimal only at this point.  I could do 
> bin2hex and hex2bin later.
>
> The strings should be the same.  I haven't got an algorithm to do this 
> automatically.  I did it manually.  I just started with all 9s, (9, 
> 99, 999, and so on) until the results differed.  Then I reduced the 
> first 9 to 1, and the rest of the 9s to 0s.  Then I increased the last 
> digit from 0 through 9 to ensure they were all the same.  If it's the 
> same, go half way up, else go half way down on the most significant 
> digit until you isolate the highest you can make it.  For example, 
> take the first digit from 1 to 5, and the last from 0-9.  If it' the 
> same, take the first up to 7, last 0-9.  I found that sometimes the 
> number would (seemingly at random) match and then differ with the last 
> digit changes. If this happens, it's considered an overflow 
> somewhere.  Usually the overflow caused the least significant digit(s) 
> to go to 0.  But sometimes it would make odds round down to evens, 
> usually 2 or 0 though.
>
> It's hard to explain.  If you come up with a good algorithm, let me 
> know.  I think it would be handy to have a quick, automatic way of 
> determining your browser's math limits.  Either way, if you've got 
> about 5-10 minutes to kill, please test this.  You can easily start 
> off where I was to save time.  A dec <-> hex converter might be handy, 
> so if it might be useful, I'll include later.  The odd looking decimal 
> number held little meaning for me until I converted it to hex and was 
> surprised to find a pretty number, which I don't believe is 
> coincidence.  :p  It's probably a C #define in some header file of 
> some math library in Mozilla.  Simply making it bigger and recompiling 
> might work locally, but does nothing for the default installs out 
> there.  Maybe there's an archaic way to change it in some browser 
> config file.  But I kind of doubt that.
>
> Leif
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted 
> by HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>
>

[Dynapi-Dev] Browser limitations of big integers.

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

Hello,

I don't know if anyone has followed the bug report for 1232705.  An 
issue is raised about big integer support.  For the purposes of this 
context, big integers shall be anything bigger than 32-bits, either 
signed or unsigned, and may herein be expressed in either hex or decimal 
(preferably both).

The biggest/smallest integer I can get in Mozilla Firefox on WinXP 32 is 
+/- hex 20 0000 0000 0000 or dec 9007199254740992.  I have not tested in 
Linux yet.  Can anyone on other OSes or browsers get bigger or smaller 
numbers?  I wrote a simply JavaScript to help, and attached it to the 
bug report.

The JavaScript page merely has some buttons with predefined numbers, an 
input field, a parse button, and an output field.  The "parse" button 
takes the string representation in the input text field, passes it to 
parseInt to make an integer.  Then it assigns that integer to the value 
of the output text field, which implicitly converts back to a string. 
The strings expect decimal only at this point.  I could do bin2hex and 
hex2bin later.

The strings should be the same.  I haven't got an algorithm to do this 
automatically.  I did it manually.  I just started with all 9s, (9, 99, 
999, and so on) until the results differed.  Then I reduced the first 9 
to 1, and the rest of the 9s to 0s.  Then I increased the last digit 
from 0 through 9 to ensure they were all the same.  If it's the same, go 
half way up, else go half way down on the most significant digit until 
you isolate the highest you can make it.  For example, take the first 
digit from 1 to 5, and the last from 0-9.  If it' the same, take the 
first up to 7, last 0-9.  I found that sometimes the number would 
(seemingly at random) match and then differ with the last digit changes. 
If this happens, it's considered an overflow somewhere.  Usually the 
overflow caused the least significant digit(s) to go to 0.  But 
sometimes it would make odds round down to evens, usually 2 or 0 though.

It's hard to explain.  If you come up with a good algorithm, let me 
know.  I think it would be handy to have a quick, automatic way of 
determining your browser's math limits.  Either way, if you've got about 
5-10 minutes to kill, please test this.  You can easily start off where 
I was to save time.  A dec <-> hex converter might be handy, so if it 
might be useful, I'll include later.  The odd looking decimal number 
held little meaning for me until I converted it to hex and was surprised 
to find a pretty number, which I don't believe is coincidence.  :p  It's 
probably a C #define in some header file of some math library in 
Mozilla.  Simply making it bigger and recompiling might work locally, 
but does nothing for the default installs out there.  Maybe there's an 
archaic way to change it in some browser config file.  But I kind of 
doubt that.

Leif

[Dynapi-Dev] [ dynapi-Bugs-1232705 ] SQL bigint values lost in SODA object transit

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

Bugs item #1232705, was opened at 2005-07-05 08:02
Message generated for change (Comment added) made by warp9pnt9
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=1232705&group_id=5757

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: conanDrum (conandrum)
Assigned to: L W (warp9pnt9)
Summary: SQL bigint values lost in SODA object transit

Initial Comment:
I believe the title says it all.
When you access an SQL database and retrieve a bigint 
value, then stick this into a dictionary object (VB ASP) 
and return the object to the client (JS HTML), the value 
on the client is recognised as [NULL].

If you return the value in a string all is well.

In General the behaviour is as follows:

Return value as:        Results in:
integer                 Overflow Error
array                   [NULL] value
object                  [NULL] value
string                  OK

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

>Comment By: L W (warp9pnt9)
Date: 2005-07-07 22:15

Message:
Logged In: YES 
user_id=706287

I've sent an email to the submitter's users.sourceforge.net
address and CCed to DynAPI-Dev mailing list.  No response
from the submitter.  Pasting the message here.  Subsequent
followup afterwards.

---- BEGIN COPY ----
Hi.  I'll try to help you with this so we can both better
understand what's going on.  Please be patient with me. 
It's been a while since I touched ASP, and currently do not
have a test platform.  At present I am only aware of
http://domaindlx.com/ with their free ASP hosting with
Microsoft Access via connectionless DN with ADODB.

If you provide a specific example of what you are trying to
do, what you are expecting, and what you are observing, then
I will be much closer to understanding the situation. 
Please do the following to help me:

1) Isolate the specific example of the code that causes the
problem.
2) Duplicate the error at DomainDLX.
3) Zip up the files and send to me with your commentary.

This will greatly help speed up the process.  Wether it's a
bug in the code, or in the documentation, or something else,
I am not sure so I can't rule anything out at this point.
---- END COPY ----

Upon some inspection of the relevant bits of code, it seems
perfectly normal that the data is sent back and forth as
text strings.  It was designed to do this.  So I have to
wonder about what is meant by "bigint".  Can you further
describe the "bigint" you refer to? Number of bits (or
min/max), signed or unsigned, and so on.

Take such a number in plain JavaScript on your client. 
Write it as a string, and then pass that string to
JavaScript's "parseInt".  I think it may be a limitation of
the browser's parseInt, or perhaps the client browser's
architechture doesn't support a "bigint", or the client
program wasn't compiled with support for "bigints".  I don't
think it has anything to do with SODA.  It's just in the
middle passing strings.  It relies on "parseInt", which
relies on the browser, which relies on the math library,
which may rely on the OS and CPU.

But to be completely sure, please test and report the
results.  I expect you'll confirm my guess.  Otherwise I'll
just close this and file it as "not a bug".  But if people
are going to be using this for bigints, I'll have to update
the documentation with this particular "gotcha".

Try to test the attached HTML + JavaScript file and use
trial and error to find the biggest number that you enter
(as a string), and can parse (as an int) and display (as a
string again), without losing digits.  The biggest/smallest
I can get is +/- hex 20 0000 0000 0000 or dec 9007199254740992.

Bottom line: you can only use ints that your client's
parseInt supports.  If you're not doing arithmetic
operations on the bigint, then just use it as a string.  If
you've got to do arithmetic operations, you've got to test
your browser capabilities and use only int sizes that are
supported.

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

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

Re: [Dynapi-Dev] [ dynapi-Bugs-1232705 ] SQL bigint values lost in SODA object transit

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

> ----- Original Message ----- 
> From: "SourceForge.net" <no...@so...>
> To: <no...@so...>
> Sent: 2005 July 05 Tuesday 08:02
> Subject: [Dynapi-Dev] [ dynapi-Bugs-1232705 ] SQL bigint values lost 
> in SODA object transit
> Summary: SQL bigint values lost in SODA object transit
>
> Initial Comment:
> I believe the title says it all.
> When you access an SQL database and retrieve a bigint
> value, then stick this into a dictionary object (VB ASP)
> and return the object to the client (JS HTML), the value
> on the client is recognised as [NULL].
>
> If you return the value in a string all is well.
>
> In General the behaviour is as follows:
>
> Return value as:        Results in:
> integer                 Overflow Error
> array                   [NULL] value
> object                  [NULL] value
> string                  OK

Hi.  I'll try to help you with this so we can both better understand 
what's going on.  Please be patient with me.  It's been a while since I 
touched ASP, and currently do not have a test platform.  At present I am 
only aware of http://domaindlx.com/ with their free ASP hosting with 
Microsoft Access via connectionless DN with ADODB.

If you provide a specific example of what you are trying to do, what you 
are expecting, and what you are observing, then I will be much closer to 
understanding the situation.  Please do the following to help me:

1) Isolate the specific example of the code that causes the problem.
2) Duplicate the error at DomainDLX.
3) Zip up the files and send to me with your commentary.

This will greatly help speed up the process.  Wether it's a bug in the 
code, or in the documentation, or something else, I am not sure so I 
can't rule anything out at this point.

Leif
warp9pnt9

P.S. FYI: the bug report is also sent to the 
dyn...@li... mailing list.  I notice that you are 
not subscribed.  You may want to subscribe there.  Posts are only 
allowed if you subscribe, as a simple yet highly effective anti-spam 
measure.  Subscription is easy.  Send a message to 
dyn...@li... with "subscribe" (without the 
quotes), as the subject or message body.

[Dynapi-Dev] [ dynapi-Bugs-1232705 ] SQL bigint values lost in SODA object transit

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

Bugs item #1232705, was opened at 2005-07-05 08:02
Message generated for change (Settings changed) made by warp9pnt9
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=1232705&group_id=5757

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: conanDrum (conandrum)
>Assigned to: L W (warp9pnt9)
Summary: SQL bigint values lost in SODA object transit

Initial Comment:
I believe the title says it all.
When you access an SQL database and retrieve a bigint 
value, then stick this into a dictionary object (VB ASP) 
and return the object to the client (JS HTML), the value 
on the client is recognised as [NULL].

If you return the value in a string all is well.

In General the behaviour is as follows:

Return value as:        Results in:
integer                 Overflow Error
array                   [NULL] value
object                  [NULL] value
string                  OK

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

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

[Dynapi-Dev] [ dynapi-Bugs-1232705 ] SQL bigint values lost in SODA object transit

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

Bugs item #1232705, was opened at 2005-07-05 15:02
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=1232705&group_id=5757

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: conanDrum (conandrum)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQL bigint values lost in SODA object transit

Initial Comment:
I believe the title says it all.
When you access an SQL database and retrieve a bigint 
value, then stick this into a dictionary object (VB ASP) 
and return the object to the client (JS HTML), the value 
on the client is recognised as [NULL].

If you return the value in a string all is well.

In General the behaviour is as follows:

Return value as:        Results in:
integer                 Overflow Error
array                   [NULL] value
object                  [NULL] value
string                  OK

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

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

Re: [Dynapi-Dev] IE Leak detector

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

> Doug Melvin; 2005-06-03@06:51 -0400
>
> Found this listed on slashdot.
> I haven't given it a thoughrou ringhing out but it looks pormising.
>
> http://jgwebber.blogspot.com/2005/05/drip-ie-leak-detector.html

That looks excellent!  I was just wondering if such a tool might exist, 
as it is sorely needed!  Thanks for the link.  I hope it works.  I'll 
have to research those Mozilla leak detectors too.



FYI: Regarding the mailing list archives at SourceForge.  Something to 
be aware of.  When you post email as an HTML message, it is sent as an 
attachment.  Even the text-only copy (if any) is sent as an attachment. 
SourceForge's mailing list archive policy is to unconditionally remove 
all attachments for web display.  So if someone is searching the 
SourceForge archive for "leak", they will match on the subject line but 
there will be no message at all.  :-\  The Mail Archive intelligently 
displays HTML messages.  For best compatibility, send text-only.  No 
idea if or when SourceForge will ever change their policy, or if the 
attachments are left intact deeper in their system (database, mail box 
file, where ever that stuff these things).

Compare SourceForge:

https://sourceforge.net/mailarchive/forum.php?forum_id=6501

With The Mail Archive:

http://www.mail-archive.com/dyn...@li.../


Leif

[Dynapi-Dev] IE Leak detector

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

Found this listed on slashdot.
I haven't given it a thoughrou ringhing out but it looks pormising.

http://jgwebber.blogspot.com/2005/05/drip-ie-leak-detector.html

Re: [Dynapi-Dev] [ dynapi-Bugs-797831 ] an on-line short questionnaire please

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

Ehh, sorry about that one.  :p  Forgot that it would go to the list. 
Was just closing this obviously bogus "bug" report.  One less to worry 
about.  :-)  Got to entertain myself somehow when doing a boring job 
like cleaning up the archives.  ;-)

Leif

>> >Comment By: L W (warp9pnt9)
>> Date: 2005-06-01 00:33
>>
>> Message:
>> Logged In: YES
>> user_id=706287
>>
>> This was no bug.  It was an unsolicited message submitted as
>> a bug.  Please do not bug us with invalid bugs.

Re: [Dynapi-Dev] [ dynapi-Bugs-797831 ] an on-line short questionnaire please

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

Sheesh.. a little out of the box eh?

----- Original Message ----- 
From: "SourceForge.net" <no...@so...>
To: <no...@so...>
Sent: Wednesday, June 01, 2005 12:33 AM
Subject: [Dynapi-Dev] [ dynapi-Bugs-797831 ] an on-line short questionnaire
please


> Bugs item #797831, was opened at 2003-08-30 13:15
> Message generated for change (Comment added) made by warp9pnt9
> You can respond by visiting:
>
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=797831&group_id=5757
>
> Please note that this message will contain a full copy of the comment
thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: None
> Group: None
> >Status: Deleted
> >Resolution: Invalid
> >Priority: 1
> Submitted By: Charles Luo (qcharles)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: an on-line short questionnaire please
>
> Initial Comment:
> Hi
>
> http://www.my3q.com/home2/21/cluo/88170.phtml
>
> Please forgive me to borther you with my short on-line
> questionnaire, although I've known that you probably
> have received the mails like this before.
>
> Currently, I am a student of Durham Business School
> (UK), striving on completing the writing of my MA
> dissertation. I just need to borrow your
> SEVEN minutes (I promise, have timed it)to help me run
> to the completion of my
> dissertation. Please............
>
> The aim of this questionnaire is to understand how
> people reflect on the
> importance of trust and collaboration to the success of
> projects (e.g.
> Open Source Software Development) carried out in a
> virtual environment.
>
> And that will be much much appreaciated if you could
> forward the above questionnaire link to your project
> members, colleagues, and friends.
>
> Thank you.............
>
> Best regards,
> Charles Luo
>
>
> ----------------------------------------------------------------------
>
> >Comment By: L W (warp9pnt9)
> Date: 2005-06-01 00:33
>
> Message:
> Logged In: YES
> user_id=706287
>
> This was no bug.  It was an unsolicited message submitted as
> a bug.  Please do not bug us with invalid bugs.
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
>
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=797831&group_id=5757
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>

Re: [Dynapi-Dev] DynAPI eye candy!

[Fausto <fau...@co...>]

Marcello,


I loved your site (www.stela....). How busy are you? Would you develop =
from a distance via net for another country? I am looking for intranet =
development using DynAPI and lots of database stuff.

Give me a note about it, please.

Fausto.


  ----- Original Message -----=20
  From: Marcelo Domingos=20
  To: dyn...@li...=20
  Sent: Saturday, May 21, 2005 3:18 PM
  Subject: [Dynapi-Dev] DynAPI eye candy!


  Hello every body!

  I've been developing a java framework which is agnostic related to GUI =
tecnology. For the first version was developed a driver based on DynAPI =
kernel. If you got interested in having some eye candy on what DynAPI =
can do for you, than take a look at site =
http://www.stela.org.br:8080/cvlattes2.

  I don't now how long the site will be kept working but for while it =
is. There, you will find a Curriculum Vitae X-Internet application =
(Brazilian Portuguese), which will be soon released officially at =
http://www.cnpq.br. The site, some times, is quite slow so don't get =
disappointed, the problem is our band-width.

  I did some improvement to DynAPI kernel (based on DynAPI 3.x beta) and =
now it knows how to handle layouts.

  Obs.: The GUI widgets are not free (for while ;) ).

  Best regards!

  Marcelo Domingos


-------------------------------------------------------------------------=
-----
  MSN Messenger: converse com os seus amigos online. Instale gr=E1tis. =
Clique aqui. 

[Dynapi-Dev] Re: [ dynapi-Bugs-797831 ] an on-line short questionnaire please (INVALID BUG)

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

Sorry, forgot it would be posted here too.  Just me pruning the mail 
archives and randomly closing an old invalid bug report from this 
misdirected message.  :-)

Leif