This raises an interesting issue though. If bugs are meant to be reported to the site and patches are also meant to be posted there, who is in charge of keeping it up to date. I see that there are some bugs listed there that are obviously fixed (PathAnimation.run() bug for eg.).
I'm not saying that having it on the site is a bad thing. I just find that the site is often behind the latest code and still lists bugs that don't exist anymore.
It is also a bit annoying to find bugs that are not actually caused by code in the API. (eg custom Array.splice problem).
I just feel that while most comunication is done using the list, it doesn't help to have the major areas of being behind the current code. is it possible to make a list of bugs that have been fixed but are not in the offical release. this should at least stop posts being sent after the bug is fixed.
Pascal Bestebroer wrote:
uhm.. hehe, Robert fixed this yesterday for the new code.. man, this is scary! :-)it was indeed the problem :) Pascal Bestebroer--
[EMAIL PROTECTED]
http://www.dynamic-core.net-----Oorspronkelijk bericht-----I've done it. and you'll kick yourself at how simple the solution was.
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Namens Michael Pemberton
Verzonden: zondag 11 maart 2001 14:21
Aan: [EMAIL PROTECTED]
Onderwerp: [Dynapi-Dev] KeyEvents working in NS6KeyEvent had to be renamed!!
and, yes, that was all that was needed. It seems that the event object triggered by NS6 was creating a KeyEvent method but because we had overwritten it with our own, it was sending out the wrong object.
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
