This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Request Procesor warning and ArrayIndexOutOfBoundsException ....work with form | ||
---|---|---|---|
Product: | platform | Reporter: | dmladek <dmladek> |
Component: | -- Other -- | Assignee: | David Simonek <dsimonek> |
Status: | CLOSED FIXED | ||
Severity: | normal | CC: | jtulach |
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | IDE log |
Description
dmladek
2000-08-31 17:25:30 UTC
Created attachment 126 [details]
IDE log
Yarda, don't you know what may be wrong? You wrote the code and I simply don't know what may cause the trouble. Thanks. I think that the problem is that some code is accessing swing in non-AWT thread (in request processor). So we should transfer the execution to AWT thread. Question is where? Dafe, should not WorkspaceImpl.setVisible use invokeLater? I agree, I can fix this. But the problem is bigger - I saw similar situation at least ten times and this leads mne to conclusion that something is bad with request processor. Request processor should allow clients to specify (optionally) that given task will run in AWT. Look at the stack - invoker *knows* that this is some swing operation... Fixed, iconify code is now called from AWT properly. (I will also add to the same place of code Yarda's further workaround for JKD's problem on KDE soon...) Marked as Verified OK, it's too old and the problem with new builds dismised Resolved for 3.4.x or earlier, no new info since then -> closing. |