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:

<[EMAIL PROTECTED]>
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.

> <[EMAIL PROTECTED]>
> 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
Dynapi-Dev@lists.sourceforge.net
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/




-------------------------------------------------------
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
Dynapi-Dev@lists.sourceforge.net
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/

Reply via email to