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.
Summary: | Mode should have getState method | ||
---|---|---|---|
Product: | platform | Reporter: | maxnitribitt <maxnitribitt> |
Component: | Window System | Assignee: | issues@platform <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | err |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | Macintosh | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
maxnitribitt
2009-07-29 20:35:52 UTC
i'm not convinced that the 'state' should be part of the generic window system api. it seem more like an attribute of a concrete ws implementation. As I see it the state is already part of the public API: You can set it's default state declaratively to "joined" or "separated" in the xml configuration file. > not convinced that the 'state' should be part of the generic window system api
Are you suggesting that
docked = SwingUtilities.getWindowAncestor( topcomponent ) == WindowManager.getDefault().getMainWindow();
is the recommended method for determining this information?
Is there some other approach/api that you are considering?
|