Return-Path: Delivered-To: apmail-xmlgraphics-batik-users-archive@www.apache.org Received: (qmail 18836 invoked from network); 7 Apr 2006 13:56:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Apr 2006 13:56:25 -0000 Received: (qmail 32861 invoked by uid 500); 7 Apr 2006 13:56:15 -0000 Delivered-To: apmail-xmlgraphics-batik-users-archive@xmlgraphics.apache.org Received: (qmail 32826 invoked by uid 500); 7 Apr 2006 13:56:14 -0000 Mailing-List: contact batik-users-help@xmlgraphics.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: batik-users@xmlgraphics.apache.org Delivered-To: mailing list batik-users@xmlgraphics.apache.org Received: (qmail 32815 invoked by uid 99); 7 Apr 2006 13:56:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Apr 2006 06:56:14 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [140.32.72.13] (HELO rcvr.je.jfcom.mil) (140.32.72.13) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Apr 2006 06:56:03 -0700 X-SBRS: None X-IronPort-AV: i="4.04,96,1144036800"; d="scan'208,217"; a="3754524:sNHT55626776" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65A4A.F113D429" Subject: Issues with timing?? Date: Fri, 7 Apr 2006 09:55:34 -0400 Message-ID: <523D779E0FF8A2468663A738B844AD0504B7D246@postman.j9.root2k.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issues with timing?? Thread-Index: AcZaSvIg1XMBVGDATei1bJ8NBR+5MA== From: "Bishop, Michael W. CONTR J9C880" To: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C65A4A.F113D429 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable OK, I'm still doing whiteboarding over a network. I've run into some kind of issue with waiting for the GVT tree. I've been calling invokeAndWait() to ensure one thread is finished before the next thread starts. All my threads that update the document are called in the RunnableQueue. However, some of these commands cause the document to be changed. If you create a new whiteboard or switch pages of a whiteboard, a new SVGDocument is put in place. Within the thread that causes the change, I try to wait for the GVT tree to finish rendering, but the GVT won't render until the current thread (also in the RunnableQueue) finished. =20 Is this correct? Basically I have a timeout while waiting for the tree to render and after the wait is over, the tree renders. I think it's backed up behind my thread in the RunnableQueue. Can I safely use invokeLater and guarantee that my threads start AND finish, one after the other? Can I "force" the GVT tree to render inside my own thread instead of waiting for it? How can I work around this issue? =20 Michael Bishop ------_=_NextPart_001_01C65A4A.F113D429 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

OK, I’m still doing whiteboarding over a = network.  I’ve run into some kind of issue with waiting for the GVT tree.  = I’ve been calling invokeAndWait() to ensure one thread is finished before the next = thread starts.  All my threads that update the document are called in the RunnableQueue.  However, some of these commands cause the document = to be changed.  If you create a new whiteboard or switch pages of a = whiteboard, a new SVGDocument is put in place.  Within the thread that causes the = change, I try to wait for the GVT tree to finish rendering, but the GVT won’t = render until the current thread (also in the RunnableQueue) = finished.

 

Is this correct?  Basically I have a timeout = while waiting for the tree to render and after the wait is over, the tree = renders.  I think it’s backed up behind my thread in the RunnableQueue.  Can I = safely use invokeLater and guarantee that my threads start AND finish, one after = the other?  Can I “force” the GVT tree to render inside my = own thread instead of waiting for it?  How can I work around this = issue?

 

Michael Bishop

------_=_NextPart_001_01C65A4A.F113D429--