Community
Participate
Working Groups
Build ID: M20080221-1800 If you use DebugUITools to launch a process, and/or if you need to display a console for a process to users in some situations, the console will popup automatically both on process launch and every time the output changes. It's great that there are toolbar buttons to allow the user to turn this off if they so desire. However it's a real problem that there's no way that a plugin developer can prevent the Console view from appearing (and continually taking the focus whenever output changes). For example, I have a heavily simplified perspective for new users and when they launch a process I don't want the Console view to popup as it will confuse them unnecessarily and also messes up the (supposedly "fixed"!) perspective layout I want them to see. However there's absolutely no way to do this, short of the gross hack of making my plugin change the console's preferences to disable the auto-popup, then revert the settings to whatever the user wants when they leave my perspective - clearly disgusting. Would it be possible to have a console extension that allows a class to decide to veto auto-popup and/or activation of the console? Or just fix the popup/activation code so it takes account of Activities - I've tried created an activity that blocks the ConsoleView but although this hides the console from "Show View" menus the activity manager is unfortunately not consulted before the view is automatically popped up. This would be quite an easy way to fix this issue, at least for what I need. Aside: There's also an argument for adding a generic mechanism for preventing *any* view from arbitrarily showing/activating itself (either based on activities or some other extension). It's not good that plugin authors have no control over cheeky views that try to do this. Maybe views should be prevented from being shown/activated even programatically if disabled by an activity? I guess this might be more work/less realistic than just getting the issue with the console view fixed, which is the main issue in the short term.
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.
