This is the mail archive of the
mailing list for the Mauve project.
Re: Tweaking default java.awt.Robot settings
- From: Lillian Angel <langel at redhat dot com>
- To: Steve McKayâ <smckay at google dot com>
- Cc: Thomas Fitzsimmons <fitzsim at redhat dot com>, David Herron <David dot Herron at sun dot com>, mauve-discuss at sources dot redhat dot com, Dan Kegel <dkegel at google dot com>
- Date: Thu, 04 Oct 2007 09:04:26 -0400
- Subject: Re: Tweaking default java.awt.Robot settings
- References: <email@example.com> <46F8238C.firstname.lastname@example.org> <46F95466.email@example.com> <firstname.lastname@example.org> <46F96854.email@example.com> <firstname.lastname@example.org> <email@example.com>
Looks good, I tested it out and committed it for you:
2007-10-03 Steve McKay <firstname.lastname@example.org>
* gnu/testlet/java/awt/Component/keyPressTest.java: Fixed test so
event is not created and dispatched. Completely waits for the
receive and respond keypress events.
Steve McKayâ wrote:
Here's a patch for the test. Everything seems to be working well. I
haven't looked through the other tests yet to see how this might be
On 9/25/07, Steve McKayâ <email@example.com> wrote:
Even after you've ensured that the frame has responded, subsequent checks will
still need to be synchronized, since Robot calls are not synchronous.
That was just a code snippet to demonstrate how to solve one part of
the problem. The code that does the actual testing is synchronized on
the lock as well. But like I said, there were liveness issues. I'll
try to work those out. Still, I can't honestly say that I'd want to go
through the same amount of effort for every test involving Robot, so
this change is sorta speculative rather than practical.
Steve McKay <firstname.lastname@example.org>