Community
Participate
Working Groups
Build: F1 Open the import dialog. Import something the will take several minutes.
[Did not finish logging it. Bugzilla!]. 1) Make sure you have more than one window with a Java Perspective active. 2) Open the import dialog. 3) Import something the will take several minutes. * Import all external plugins for example. 4) Don't wait it to finish. 5) Using "ALT+TAB", got to another window. 6) Press CTRL+SHIFT+T, type a name of a class and enter. Eclipse is not thread safe and we may end up getting all sort of errors. The import dialog is modal. It should not let the user do something else in another window.
Should have opened in SWT. The dialog acts like modal if you try to access another window using the mouse; the problem happens only when using accelerators.
Accelerators can not be active while a modal dialog is running. Must fix.
Fixed > 20020527.
I'm still experiencing this in build 20020530 on Win2k. Should the fix be in this build? I was very easily able to deadlock eclipse by starting builds from two windows at once.
I'm sorry... this appears to be a different case. I just noticed that the incremental build doesn't use a modal dialog anymore, it just uses a busy cursor. This may not be an SWT problem, I will file a new bug.
The deadlock you saw is probably due to bug 2229 and is not an SWT problem.
John, please see previous comment.
Still a problem in build 0618. I think this should be considered for F4. Steps: 1) Open two workbench windows. 2) Open a modal dialog in one (File->Import) 3) Use Alt+Tab to go to the other window. 4) Use Alt+Char to get to a menu (Alt+N T for example to open type in the Java Perspective)
Steve, please investigate. Let me know as soon as you know what's going on.
I have a fix in hand. It is low risk. It involves testing for "disabled && modal" in one place instead of testing only for "disabled". We should put it in.
Fixed > 20020619