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.

Bug 25578 - Redesign the property event managing of TopComponent with WindowManager.TopComponentManager
Summary: Redesign the property event managing of TopComponent with WindowManager.TopCo...
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords: ARCH
Depends on:
Blocks:
 
Reported: 2002-07-12 11:11 UTC by Peter Zavadsky
Modified: 2008-12-23 09:46 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zavadsky 2002-07-12 11:11:04 UTC 
See the #issue 19428.
There seems to be very problematic, listening on
TopComponent property changes via its
WindowManager.TopComponentManaget.

It seems to me much more efficient and clear would
be to listen directly for property changes of TC
which acts like ordinary swing component.
Thus it would be much easier to enhance new
properties added to it and extending possible
handling.
Comment 1 Marek Grummich 2002-07-22 08:32:50 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 2 Marek Grummich 2002-07-22 08:42:58 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 3 Marian Mirilovic 2003-11-26 12:57:45 UTC 
Because Window System v1 will not be supported from now by our team, all old
winsys issues (now "core/window system v1" issues) are going to be closed as
WONTFIX. 

Changes in API which emerged both from UI spec 
and problems with adjusting to the older API are described in the document
http://core.netbeans.org/windowsystem/changes.html.
 It shows also recommends how the client code should be adjusted to the new
window system.

If you think this issue apply also to the new winsys then change the
subcomponent (to "core/window system") and REOPEN it.
Comment 4 Marian Mirilovic 2004-02-27 14:12:33 UTC 
issue doesn't apply to new window system - verified