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.
Redesign the GUI startup creation to follow typical GUI creation concept, i.e. for MDI: 1) The main frame and is created. 2) All the containers and components are created and their bounds correctly set if needed (before the pack call), then added to the main window hierarchy. 3) It is called pack, and show (setVisible(true)) on the main frame. Currently the bounds are determined by early pack call on the main window to be found out later from going-to-be-added components. The containers and components are adding afterwards inbetween the pack and show calls, as a response in various event handlers, which leads to the unwanted flash effect on Win platform. The main problem will be to found out the way of determining the bounds for adding components (or mode containers respectivelly).
Can't guess, how much of work is required, setting the milestone to future, but I'll try to succed to do it to 4.0. Marek could provide a better guess.
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.
issue doesn't apply to new window system - verified