Dialog placement and misplaced dialog observations

[errael]

The idea with this discussion is to gather information for a NB-17 PR. Can be thought of as a followup to #4739.

In a multi screen setup, I still occasionally see dialogs that show up on the default screen, rather than where the action is. Dialogs should generally be either be on/around NetBeans' main window or some active window. Often times can't replicate a misplacement problem.

I've opened this discussion to collect information on dialogs that are misplaced or aren't placed very well. I'm hoping to address some of them for NB-17. If you come across any problems/issues with dialog placement, you're welcome to add a comment to this issue.

[errael]

These observations are based on a screen setup with NetBeans's MainWindow on screen-1, the default location is screen-0.

ide/projectui/src/org/netbeans/modules/project/ui/problems/BrokenReferencesImpl.java
First startup with NB-16-rc4, using nb15 userdir. OpenProject-ResolveProblem diaglog, uses DialogDisplayer.getDefault().notify(dd). Tried several times dialog shows up on any of 3 screens.

platform/core.execution/src/org/netbeans/core/execution/Install.java
Exit IDE pending tasks dialog. With NB on screen 1, dialog showed up on screen 0 (default). Dialog created in showPendingTasks(), needs examination but first glance doesn't show a parent being set. Does DialogDisplayer.getDefault().createDialog(dd)

track down location
Start NB under debugger, clean udir. Move from screen 0 to screen 1. Tools>Options dialog comes up in screen 1. Click Java. Options redraws in screen 0.

track down location
Find Usages occasionally goes to screen 0 rather than MainWindow's screen.

track down location
jVi Warning about SiftWidth... occasionally goes to screen 0.

track down location
Inspect and Transform; No Pattern Found

[errael]

Comment from @sdedic in #5280 (comment)

Related to existing 'nearby' code: this method uses KeyboardFocusManager.getCurrentKeyboardFocusManager().getFocusedWindow() while getCurrentGraphicsConfiguration() (in diff below) uses KeyboardFocusManager.getCurrentKeyboardFocusManager().getFocusOwner() then getWindowAncestor(). Deliberate difference or inconsistency ?