Pressing F1 on a dialog (NbDialog) that has a DialogDescriptor with a specified help context generally does not work. It does occasionally--it seems, the first time a dialog is opened--but thereafte
r F1 seems to be running the global HelpAction instead. For some reason the dialog is not properly trapping the keystroke.

Test case: PropertyDialogManager from the property sheet now adds a help context if the custom property editor specifies one on itself. The ErrorDescriptions editor does this (e.g. external compilatio
n settings). Pressing F1 on this custom editor should pop up help or an error for ErrorDescriptions, but usually it gives one for default help (the result of HelpAction). Specifically, if you open the
 custom editor and immediately press F1, *both* actions will run; thereafter, only HelpAction will, and it will of course not find the right help since it looks for a top component.

HINT: TopComponent.FocusMan does not seem to know when a dialog is open.

------------------------------------------------------------------------------
[Old suggestion:]

E.g. on custom property editors (though a Help button is now displayed for this purpose anyway).

HelpAction should have public static methods:

  public Window getFocussedWindow () {...}
  public void setFocussedWindow (Window w) {...}


and should look on that window for help. Then window manager impl should set this whenever window switch occurs, either to MultiObjectFrame, SingleObjectFrame, MainWindow, etc. Also, the dialog create
d by TopManager.notify should temporarily set this window to the dialog, until it is closed.