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.
Now we have run/debug buttons on the toolbar but if you have more than one project opened it is really dangerous to use them - you do not know which one it will start/debug... It forces me to use project context menu and do run/debug from there. That would be very useful to have run/debug buttons directly in the projects view. The same idea is implemented already in the Debugging view where we have separate resume button for every thread available.
No plans to change this UI that I know of. (In reply to comment #0) > if you have more than one > project opened it is really dangerous to use them - you do not know which one > it will start/debug The main project, if set, else the selected project. Same for the keyboard shortcuts. > [it] would be very useful to have run/debug buttons > directly in the projects view. As a toolbar in the Projects tab? That would make no difference, as the buttons would still be sensitive to the current selection. > in the Debugging view where we have separate resume button for every thread I guess you mean the (tree?) table view where a column is occupied (by default) with a suspend/resume button. But for the Projects tab, we would need a Run button, a Debug button, a Profile button, a Build button, a Clean & Build button, maybe more contributed by modules, ... which would all take significant horizontal space and clutter the display.
maybe I was wrong giving solutions, my problem is: I develop a NB module, contained in a suite. I modify files in the module and run/debug the suite. If I'm editing a file and click on run/debug button on the toolbar it starts the action for the module, not the suite. Setting main project also does not help, because sometimes I start another suite. So for me toolbar run/debug/profile buttons are useless and I always use project context menu. At least it is 100% predictable.
(In reply to comment #2) > I develop a NB module, contained in a suite. I modify files in the module and > run/debug the suite. If I'm editing a file and click on run/debug button on the > toolbar it starts the action for the module, not the suite. This is often fine - just builds that one module and starts the app - though you might specifically want to build all modified modules, or have custom run logic in ${suite.dir}/build.xml, etc. > for me toolbar run/debug/profile buttons are useless You can simply change the selection to the desired project (e.g. in Projects) before running one of these actions. That works well for keyboard shortcuts; in the case of toolbar buttons it is less helpful (when multiple projects are open), since the gesture of first selecting the project and then moving the mouse to a toolbar button is not necessarily smoother than right-clicking the project and selecting a context menu item. Personally I always turn off toolbars anyway (waste of space and clumsy to use) so I have no idea about whether context-sensitive toolbar buttons have any value to others. My impression is that we have toolbars because people expect apps to have toolbars. HIE can decide what they want; I am not about to make a major UI change on my own initiative. (Tangentially related: the Run-like toolbar buttons used to have a dropdown so that you could immediately run a particular configuration without first switching to it, but HIE asked to drop this.)
I agree about the toolbar )) do not use it either, probably context menu action is a reasonable substitute for toolbar run/debug action