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.
I've launched NB in MDI mode and was trying to edit some Forms. I had the Explorer, Output and "Desktop" areas displayed in the GUI Editing workspace tab. I tried to open up the Component Inspector from the Form, and it happened to be already be opened in the area that was not showing in the current scrollable area of the Desktop. There was no user feedback on where the component inspector appeared (it seemed like NB didn't respond to the request, hence I kept trying to "Go to Inspector") I would suggest when user requests a window that is currently off screen the requested window should relocate and be fronted so that it appears in the scrollable area or scroll to the area where the requested window appears.
We need to think carefully about this. Other MDI implementations do not do this, since it's hard to figure out how much of the "obscured" window needs to be obscured before we scroll down to it, or move it to the center of the viewable area. We could easily end up with a very jumpy IDE. It might be worthwhile considering an alternative approach, like a "Find Window" or "Retrieve Window" command. For that matter, is it even possible, without a lot of computation, to tell whether or not a window is obscured in MDI?
Version: 'Dev' -> 3.2
I think it is possible to determine that window is scrolled away from currently shown area. However it will need some computation and also more discussion on how it should behave exactly. I tend to agree with Dirk's "Find Window" command or something similar. So, this will not be adressed in 3.2, I'm changing version back to "dev".
if the window is off of the screen when it is updated, maybe briefly show a flashing arrow or something which points towards the window. possibly clicking on the arrow scrolls you to the window... i definitely wouldn't want the window relocated. i like them where i put them.
Target milestone -> 3.3
Reassigning back to Window System guys
Target milestone -> 3.3.1.
Evaluation: Adding functionality to make window somehow visible when it is off of visible area and user requests it.
Target milestone -> 3.4
Target milestone was changed from '3.4' to TBD.
Set terget milestone to TBD
It should be fixed as MDI desktop implementation will be changed.
Clicking on Window and selecting a window to view does not change focus to that window. I don't think this would be an issue if you could cycle through the windows correctly.
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