Re: [Dynapi-Dev] KeyEvents working in NS6

[Richard Bennett]

It might help if we actually use the functions like assigned to, priority, etc that are available at source-forge. Then we would at least know if someone had taken it on themselves to look into the bug, and that it was not being forgotten. Also, I've seen so many fixes for all kinds of things pass through the list without any comment, couldn't we have somewhere to submit bugFIXES, where they would be acknowledged, and kept for reference, until they are tested and committed to CVS. Otherwise people are going to stop posting their bugfixes, because it seems the rest just don't care.   ----- Original Message ----- From: Michael Pemberton To: [EMAIL PROTECTED] Sent: Sunday, March 11, 2001 4:46 PM Subject: Re: [Dynapi-Dev] KeyEvents working in NS6 glad to see that it was solved. 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.