On Wed, Feb 23, 2005 at 06:17:31PM +0100, Meskauskas Audrius wrote:
> The javax.swing.Timer fires action events. It has two properties, one
> specifying the waiting time before firing the first action event, and another
> the time
> gap between firing the subsequent events.
>
> The new Mauve test ("basic") has indicated unusually inaccurate work of this
> class. The first action event is fired far later than requested.
>
> >From the source code it seems that the first sheduled action is not fired at
> all. The Timer only fires the second and subsequent actions.
>
> The bug can be fixed by an extra line of code.
>
> The Mauve test that found this is attached to this letter. I am not sure if
> it is worthwhile to include it to the Mauve project as it takes as many as
> five
> seconds to complete.
Thanks, please apply this patch to classpath.
I think its okay to add the testcase to Mauve. People who dont like the
5 second runtime can just disable the testcase and nut run it. We have
already testcases in mauve which take similar time to complete, some
even depend on a working network connection and some server of FSF or
RedHat available.
Michael
_______________________________________________
Classpath-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/classpath-patches
