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.
[ BUILD # : 20051101_1 ] [ JDK VERSION : 1.5.0_04 ] Why is there a difference between what happens if I right click a component in the Flow Layout and select "Go to source" and if I select the component and click the "Source" button? Wouldn't it make more sense to go to the source for the currently selected component when the "Source" button is clicked? I assume that the problem is how to handle the scenario where more than one component is selected? My suggestion is to diable the "Source" button when more than one component is selected, since this is the way the "Go to source" menu item behaves.
The "Go to Source" action is always context sensitive and gets you to place in the source code that belongs to the component of the context. On the other hand "Source" button is not context sensitive and acts like a tab handle - it allows you to switch to the source editor and you will be placed to your last editing location. It behaves the same as "Screen" and "Flow" buttons. Disabling "Source" button is not a solution. It would force user to do some additional actions before he/she is able to get to the source code (even thought he/she just want to look at something in the source code and than return back). Also by implementing this RFE you will loose possibility to work with the source code, occasionally look at the Designers and return to the same position in the source code. By implementation point of view it is not possible to disable "Source" button. I propose different solution: I think the problem is that "Go to Source" action is in the popup menu and is not visible by default. Therefore there should be some buttons/glyphs/marks placed near to each component in the Screen and Flow Designers that will acts like the current "Go to Source" action.
You solution sounds good. I guess you're right about disabling the Source button might not be the best soultion. The problem I see with adding more icons or buttons is that the interface might becmoe very cluttered. The icons will probably need to be pretty small not to interfere with transitions and ports. They might even need to reposition themselves in the event they get "covered" by a transition, unless they are somehow placed "inside" the component icon.
Yes, I fully agree that we hav to be very careful about adding new icons. The one of priorities for future release is to polish and clean-up the UI to be more intuitive and descriptive. Therefore we are also planning to change properties window to something more powerful and helpful than just a list of properties. The Flow Designer will be very tightly connected with it and "Go to Source" button could be placed into this New Properties Window. Anyway we still want to have "Source" and "Go to Source" behavior split as they are right now.
moving to mobility component