Kepler

This happened to me yesterday after I got a moml exception.

I just tried to force this to happen in the wrp and kepler suites and could not make it happen. Is this still happening for others?

I've found a way to make this happen: delete a run w/ the WRM.
Once you select delete from the context WRM context menu, you'll get a confirmation dialog, at which point the Kepler menu disappears. I suspect I'm doing something wrong with my confirmation dialog, I'll look into it...

Here are a few ways to get this to occur just using the kepler suite.

1) Drag a String Length actor to canvas.
2) Select Preview, or Upload to Repository or Save Archive or Semantic Type Annotation from the right-click context menu.

Even when you leave these menus the Kepler application menu does not reappear.

Derik, could you repro this bug on a different machine than your mac? If so, could you recomment here and tell us how you did it?

I am able to reproduce this bug following the steps in comment #4 (on my mac).

Found mention of this on the internet, not sure if it's been resolved. I tried the workflow-around mentioned (don't pass null as first param to showMessageDialog()) and that worked for me. Instead of disappearing, the menu items just gray and then properly un-gray when you're done w/ the dialog. I'll go through and change all the showMessageDialog calls that I can find if no one objects...

http://lists.apple.com/archives/Java-dev/2009/Jun/msg00197.html

Also noticed this bug doesn't happen on os X 10.6 w/ java 1.6.

Whoops - that thread does discuss showMessageDialog, but my test was to showConfirmDialog. So this likely works for both of those calls, maybe others...

The workaround in comment #7 works, and was implemented.

This bug should now serve as a reminder: before wrp-modules-1.0.0 is released, search for and fix any calls to showConfirmDialog or showMessageDialog that use null as first parameter.

I've search for possibly offending calls to showConfirmDialog and showMessageDialog (those that use null as first argument), and found only one class that does so: OntologyDisplayUI.java. Using this gui in Kepler, I'm unable to get the bug to occur (the menu items disappearing and not coming back), so these calls are probably fine as is, but we might look into if it makes sense to give as argument a parent frame.

(In reply to comment #10)

I've search for possibly offending calls to showConfirmDialog and
showMessageDialog (those that use null as first argument), and found only one
class that does so: OntologyDisplayUI.java. Using this gui in Kepler, I'm
unable to get the bug to occur (the menu items disappearing and not coming
back), so these calls are probably fine as is, but we might look into if it
makes sense to give as argument a parent frame.

Searched though the reporting suite modules, that is. I didn't search all of kepler this time.

closing, this was just left open as a reminder.

Original Bugzilla ID was 4247