Community
Participate
Working Groups
Builld id: M3 1)The global debug toolbar is always "active" when I launch my Eclipse workbench for the first time, even though no debug session is in progress. 2) The "tool bar visibility" settings do not respect the "command group visibility" settings in the "Customize persepctive.." dialog ONLY in java perspective. When I uncheck the "Debug" command group in the command groups visibility tab, and go back to "tool bar visibility", I'm allowed to select the debug option, and even expand it and select the "skip all breakpoints" option. All the other sub-options are greyed out though.
Created attachment 206764 [details] snapshot of "Customize perspective.." dialog
> 1)The global debug toolbar is always "active" when I launch my Eclipse > workbench You mean you see all action, not just the 'Skip all breakpoints' action? When I try it, I only see that one and this is as designed.
Created attachment 206788 [details] snapshot showing active debug actions (In reply to comment #2) > > 1)The global debug toolbar is always "active" when I launch my Eclipse > > workbench > You mean you see all action, not just the 'Skip all breakpoints' action? When > I try it, I only see that one and this is as designed. Basically 1) and 2) are unrelated cases here. To reproduce 1) do this: - Enable debug command group in "Customize perspective.."'s command groups availability, and then enable all debug actions under the tool bar visibility tab. - Make sure all actions appear on the coolbar and restart the workbench. - On restart, you will find that all debug actions are in a coloured active state. Expected: They should be greyed out since no debug session is in progress. (This is a very minor problem though, since when I click on any debug action, I get a dialog that this is not available and all of them grey out immediately.)
Created attachment 206789 [details] empty space in the coolbar This snapshot shows what happens in the case 2) in comment 0 i.e. when I select only the breakpoints action and disable the debug command group availability, I get an empty space in the coolbar.
Given your screenshots and the version field, I'm assuming you're using 3.8. Could you confirm this, Ayushman? Thanks.
(In reply to comment #5) > Given your screenshots and the version field, I'm assuming you're using 3.8. > Could you confirm this, Ayushman? Thanks. Yup. 3.8 indeed, though I expect these to be the same on 4.2 as well.
(In reply to comment #6) > (In reply to comment #5) > > Given your screenshots and the version field, I'm assuming you're using 3.8. > > Could you confirm this, Ayushman? Thanks. > > Yup. 3.8 indeed, though I expect these to be the same on 4.2 as well. Well, the empty space problem shouldn't happen in 4.x. I think that's a long standing bug with 3.x.
*** Bug 380231 has been marked as a duplicate of this bug. ***
Could you please have a look at bug #404348 and tell me if this is related?
Ran into problem #1 with Eclipse 3.8. Went on to try reproducing it with 4.2 and 4.3M6. Did this on Linux and Mac and noted the following (applies to 3.8, 4.2 and 4.3M6): If the Debug view is NOT shown and the Debug commands group is visible in the toolbar of the current perspective, then the Debug actions are enabled when Eclipse is launched. As soon as I open the Debug view, the actions gets disabled (as they should be).
*** Bug 404759 has been marked as a duplicate of this bug. ***
This works as designed. We explicitly do not want to load a bundle just to detect the correct enabling of its actions. The state is updated as soon as the bundle is loaded or the action executed.
*** Bug 406869 has been marked as a duplicate of this bug. ***
Why not have them disabled until the bundle is loaded and can enable them explicitly?
(In reply to comment #14) > Why not have them disabled until the bundle is loaded and can enable them > explicitly? You're right. Only the buttons that can trigger the loading, like e.g. launch something or toggle a breakpoint should be enabled. From the Debug command group only "Use Step Filters" needs to be enabled. This worked fine for the menus in 3.7, but got broken with the introduction of the global Debug toolbar.
Created attachment 230389 [details] Debug menu items in 3.7
(In reply to comment #14) > Why not have them disabled until the bundle is loaded and can enable them > explicitly? Tool and Menu items are enabled until the plugin is activated so that selecting them can be used to trigger the plugin activation. The framework can't tell which ones make sense to disable by default currently. it would have to be an opt-in enhancement added to the appropriate extension point (default enablement if the contributing plugin is not active). PW
(In reply to comment #17) > (In reply to comment #14) > > Why not have them disabled until the bundle is loaded and can enable them > > explicitly? > > Tool and Menu items are enabled until the plugin is activated so that > selecting them can be used to trigger the plugin activation. > > The framework can't tell which ones make sense to disable by default > currently. it would have to be an opt-in enhancement added to the > appropriate extension point (default enablement if the contributing plugin > is not active). In 3.7 the debug actions appeared disabled in the menu, so there must be a way to do this ;-). Only in 3.8 this got changed by the new Debug global toolbar.
Still an issue with Kepler RC2. Is there chance to get this fixed for Kepler?
It's too late for 4.3.
*** Bug 410903 has been marked as a duplicate of this bug. ***
Version: Luna (4.4) Build id: I20140422-0800 Attaching the screen shot of Toolbar. Works as expected. For point 2 of Problem Description, Dani has already provided the reason.
Created attachment 242274 [details] Global Debug Toolbar in 4.4 M7
(In reply to Sarika Sinha from comment #23) > Created attachment 242274 [details] > Global Debug Toolbar in 4.4 M7 This is a menu, not a toolbar. Attachment 206788 [details] from comment 3 shows the global toolbar.
Created attachment 242286 [details] Global Debug Toolbar in 4.4 M7 Thanks Markus. Here goes the toolbar snapshot from latest build.
N20140423-2200: new workspace, close Welcome, Window > Customize Perspective... > Command Groups Availability > check "Debug" > OK => Actions like Step Into are enabled in global toolbar and in Run menu. In 3.8.2, they were disabled and only Debug, Run, and Skip All Breakpoints were enabled in the toolbar. The enablement gets fixed once the debug plug-in is loaded (e.g. the Debug view or perspective is opened).
*** Bug 442958 has been marked as a duplicate of this bug. ***
Bug is still present in 4.4.1.
Bug is still present in 4.5.0
*** Bug 487789 has been marked as a duplicate of this bug. ***
4.6M7 has same problem as well. On linux is even worse since you can't click Terminate to make them disables.
Any updates on this? We are already in Neon.2 and the bug is still present.
(In reply to Danilo Cominotti Marques from comment #32) > Any updates on this? We are already in Neon.2 and the bug is still present. Unfortunately, no one is working on it right now. We welcome good quality patches.
Fixed since 2019-12 with bug 552350. *** This bug has been marked as a duplicate of bug 552350 ***
