Not sure if this is an issue with the current JavaVM (1.5.0_16-
b06-284) on Leopard or if this is existing since I only created a
Help menu today, but I noticed that when the Help menu (and only the
Help menu) is clicked, my app's lostFocus event fires. Then when let
go of the mouse button and the menu disappears, focus is regained.
Surely that's not an "expected behavior"? Can someone confirm or
deny if this is "bug" or a "feature"?
This is actually a regression that was introduced in Leopard GM (with
the introduction of the Help menu with the search field in it).
The fundamental problem is that the NSWindow that holds the Java
content has lost "key", but is still considered to be "main" (to use
AppKit's terminology). In Tiger and prior, there was no effective
difference between "key" or "main" from Java's perspective, so we
triggered our focus notifications off of "key". Come to find out, we
should have used "main".
We have a bug or two tracking this issue, however the replumbing of
the AWT to trigger everything off of "main" will likely be a
destabilizing change - which will have to be done carefully.
Apologies,
Mike Swingler
Java Runtime Engineer
Apple Inc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
