Community
Participate
Working Groups
the url contains my original question.. anyway the "hack" i found was to enter the plugin.xml file in org.eclipse.debug.ui , and org.eclipse.jdt.debug and remove the autoOpen and autoClose attributes completly from Expression and Display views. this way i get what i want, the variables,display and expression view appear and vanish only when i debug, thus saving me screen space. i understand why these attributes were needed before view management per perspective was added, but now it's just in the way.
I don't know if JDT can change the default behavior. Is there an ask to allow the auto-open auto-close to be customized in preferences per view?
(In reply to comment #1) > I don't know if JDT can change the default behavior. Is there an ask to allow > the auto-open auto-close to be customized in preferences per view? yes, it's the small checkbox under the perspective list managed by the debug view. unfortunately it's way too coarse to allow too control. the fd"real" solution would off course to display a view list (with 2 check boxes of open and close) per each perspective being selected above the checkbox and allow the user to define it himself. naturally this would require dynamic control over current extension points and i'm not sure it's possible, so i went with a samller idea.
Makes sense (for the real solution).
(In reply to comment #3) > Makes sense (for the real solution). i would agree, but that would require a much bigger change to the extension points, and make then dynamic. maybe even breaking backwards compatibility. so i thought about being modest.
so what's the descision on this one?
(In reply to comment #5) > so what's the descision on this one? Debug committer resources are very limited right now, so there will be no work done on the 'real' solution for this bug. We do however, accept patches.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
