Thread: [Objectscript-devel] [OBJECTSCRIPT] Issue #OBJS165 modified
Brought to you by:
rob_d_clark
Menu
▾
▴
objectscript-devel
|
From: Rob C. <rob...@ma...> - 2003-06-19 01:46:22
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() can be bad...)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Added comment to issue 'note... there appears maybe to be a bug in SwingUtilities.invokeAndWait(), which results in it not waking the suspended task until some time after the runnable has completed. I'll investigate further, but it appears that this...'
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-19 01:46:42
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() can be bad...)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Status changed from 'New' to 'Assigned'
Reason:
move to 'assigned' state
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-19 02:25:11
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() can be bad...)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Added comment to issue 'hmm, looked at EventQueue.invokeAndWait() (and InvokationEvent) and it seems pretty straightforward... perhaps related to ti.swing.SwingQueue, which seems to always be on the stack when this happens'
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-23 07:18:44
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() takes too long)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Status changed from 'Resolved' to 'Closed'
Reason:
oscript v1.3.2
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-23 07:26:52
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() takes too long)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Added comment to issue 'AUTOGENERATED CHECKIN COMMENT:
------------------------------
Author: rob...@ma...
Date: 2003-06-19 13:22:03 -0700 (Thu, 19 Jun 2003)
Files:
U branches/OBJS165/chimera/ti/chimera/plugin/WindowManagerP...'
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-23 07:26:57
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() takes too long)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Status changed from 'Assigned' to 'Resolved'
Reason:
move to 'resolved' state
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-23 07:27:03
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() takes too long)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Added comment to issue 'AUTOGENERATED CHECKIN COMMENT:
------------------------------
Author: rob...@ma...
Date: 2003-06-19 12:08:05 -0700 (Thu, 19 Jun 2003)
Files:
U branches/OBJS165/chimera/ti/swing/SwingQueue.java
Vers...'
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-23 07:27:06
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() can be bad...)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Added comment to issue 'ok, I think I get it... looks like in some cases SwingQueue may not wake up the "blocked" thread... so if dequeue() gets called (indirectly) from the runnable passed to invokeAndWait(), then the invokeAndWait() can't return'
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
|
From: Rob C. <rob...@ma...> - 2003-06-23 07:27:09
|
You can view the issue detail at the following URL:
http://icandy.homeunix.org:443/scarab/issues/id/OBJS165
Type
Defect
Issue ID
OBJS165 (Dock's use of SwingUtilities.invokeAndWait() takes too long)
Modified by
Rob Clark
rob...@ma... (rob...@ma...)
The following modifications were made to this issue:
---------------------------------------------------------------------
Headline changed from 'Dock's use of SwingUtilities.i...' to 'Dock's use of SwingUtilities.i...'
Reason:
changing summary to reflect what I now know about the cause of the problem
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X