From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18712 invoked by alias); 25 Sep 2007 20:28:36 -0000 Received: (qmail 18702 invoked by uid 22791); 25 Sep 2007 20:28:36 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 25 Sep 2007 20:28:32 +0000 Received: from zps77.corp.google.com (zps77.corp.google.com [172.25.146.77]) by smtp-out.google.com with ESMTP id l8PKSR8V029304 for ; Tue, 25 Sep 2007 13:28:27 -0700 Received: from wr-out-0506.google.com (wrac48.prod.google.com [10.54.54.48]) by zps77.corp.google.com with ESMTP id l8PKS8rf019352 for ; Tue, 25 Sep 2007 13:28:25 -0700 Received: by wr-out-0506.google.com with SMTP id c48so704062wra for ; Tue, 25 Sep 2007 13:28:25 -0700 (PDT) Received: by 10.142.49.4 with SMTP id w4mr1401641wfw.1190752104559; Tue, 25 Sep 2007 13:28:24 -0700 (PDT) Received: by 10.70.39.13 with HTTP; Tue, 25 Sep 2007 13:28:24 -0700 (PDT) Message-ID: <4f2ee4520709251328s388c16ebs46f66ce3232cb48f@mail.gmail.com> Date: Tue, 25 Sep 2007 20:28:00 -0000 From: "=?UTF-8?Q?Steve_McKay=E2=98=84?=" To: "Thomas Fitzsimmons" Subject: Re: Tweaking default java.awt.Robot settings Cc: "David Herron" , mauve-discuss@sources.redhat.com In-Reply-To: <46F96854.6080706@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4f2ee4520709241331o1a77379cudffb314dc1622914@mail.gmail.com> <46F8238C.8020606@sun.com> <46F95466.7070700@redhat.com> <4f2ee4520709251156yde57b65tbb97032939ac75e6@mail.gmail.com> <46F96854.6080706@redhat.com> X-IsSubscribed: yes Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00038.txt.bz2 Thomas, > 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