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.

Bug 207104 - IDE dialogs lock up the IDE if they appear in different Mac OS X spaces than the main window
Summary: IDE dialogs lock up the IDE if they appear in different Mac OS X spaces than ...
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: JDK Problems (show other bugs)
Version: 7.1
Hardware: Macintosh (x86) Mac OS X
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: JDK_SPECIFIC
: 209442 212621 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-01-10 08:36 UTC by markdjohnston
Modified: 2012-05-18 13:11 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description markdjohnston 2012-01-10 08:36:05 UTC 
On Mac OS X 10.7 (at least), running with multiple spaces, when certain modal dialogs open in your current space, and that space is not the one where the main IDE is running, it is impossible to dismiss or otherwise act on them. The only recourse is to force quit Netbeans. Example: Netbeans is running in Space 1, start a subversion 'show changes' command, and then switch to any other space, say Space 2. If subversion returns an error, the dialog opens in the *current* Space 2, but if you try to act on the dialog, focus returns to the original Space 1 where the dialog is inaccessible. Going back and forth between the spaces is fruitless, and your only choice is to force quit Netbeans and start over. Another example: you have a file open in Netbeans, and make a modification. You switch to another space and then another app modifies the same file. Netbeans puts up a modal dialog that the file has been modified and asks if you want to reload it. It's impossible to click "no" or "yes" on the dialog since each time you click the dialog you are returned to the main IDE space, but the dialog remains in the other space. Again, force quit is the only option.

It seems to me that *modal* dialogs must open as subordinate to the main IDE, effectively as children of the main IDE frame.
Comment 1 Stanislav Aubrecht 2012-01-12 14:56:33 UTC 
i have reproduce this behavior with a plain Swing app. it's not netbeans specific, most likely a JDK issue

a workaround is to right-click the application icon in the Dock and select 'options - all desktops' or 'options - this desktop'
Comment 2 ttokoly 2012-02-10 19:41:49 UTC 
Product Version: NetBeans IDE 7.1.1 (Build 201202092200)
JDK 7 build 228 (Developer Preview)
System: Mac OS X version 10.7.3 running on x86_64; MacRoman; en_US (nb)

I've tried to reproduce this issue with newest build of JDK and I have met different behavior.

1. Create two Spaces - 1 and 2
2. Run IDE with JDK 7 in Space 1
3. Open some file and modify it
4. Switch to Space 2 and with another app change that modified file
5. Same (reload) dialog shows in Space 2

But now, if you click on it, doesn't matter where, it "transports" you together with dialog to original IDE Space (Space 1). And than dialog works fine. So, I'm not sure if this is correct behavior, but at least it's not P2 bug. What you think?
Comment 3 Stanislav Aubrecht 2012-02-22 16:27:40 UTC 
in JDK 1.7 update 4 b11 the reload dialog appears for about 3 second at the current space and then moves automatically to the original space with netbeans.

it seems to be fixed in JDK 1.7.
Comment 4 Stanislav Aubrecht 2012-03-12 11:24:40 UTC 
*** Bug 209442 has been marked as a duplicate of this bug. ***
Comment 5 Tomas Danek 2012-03-21 15:53:07 UTC 
  Product Version         = NetBeans IDE Dev (Build 201203180400) (#3ad82e81863d)
  Operating System        = Mac OS X version 10.7.3 running on amd64
  Java; VM; Vendor        = 1.7.0_04-ea; Java HotSpot(TM) 64-Bit Server VM 23.0-b17; Oracle Corporation
  Runtime                 = Java(TM) SE Runtime Environment 1.7.0_04-ea-b16
-----------------
case 1:
- open in NB some file, modify
- switch to space 2, modify the same file externally, save
- nothing happens unless i switch back to space 1; this triggers external changes reload dialog; dialog is shown in space 1. This is IMHO correct behavior

case 2:
- start checkout from VCS
- switch to space 2
- modal dialog (NB projects were detected, do you want to open them?) appears on space 2
- clicking on dialog transfers focus back to NB to space 1; no dialog is here, but after click into NB window dialog appears and can be handled fine.
Not  very nice behavior, but no lock up happens, no need to force quit.
If you have strong opinion about this, this can be seen as some (low priority) JDK bug.
Comment 6 Stanislav Aubrecht 2012-05-18 13:11:56 UTC 
*** Bug 212621 has been marked as a duplicate of this bug. ***