Community
Participate
Working Groups
I had to debug a client-server app and found some problems: - when running, I don't see which program/process currently writes to the console (if I don't use the Debug view) - even when running in the Debug view, I have to manually switch the console to see what happens (e.g. looking at simple sample as ping-pong) Workaround: I used (detached) the consoles from two different Debug perspectives. NOTES: DW (7/16/01 8:33:37 AM) Can we change the title of the console view to show the process name?
PRODUCT VERSION: 0.9
See bug# 10300
Wrong status
Deferred
In 2.0 we display the process title in the console view. This issue is otherwise addressed in Bug 7715
*** This bug has been marked as a duplicate of 7715 ***
I noticed that this has been marked as duplicate of bug 7715. 7715 only says switching should be possible but I don't simply want to SWITCH between processes I want to see them (e.g. client process and server process output) side a side (e.g. in two consoles). Comments in 7715 don't seem to go for such a solution.
Unfortunately, the workbench framework does not allow more than one instance of a view open in one window. You could acheive this by opening two windows, and selecting different processes in each window (to see the client/server output in two consoles).
I know the workbench constraint and also the workaround. Nevertheless I'd like to work in one window (forcing me to open a second workbench window is not optimal especially since detaching is no longer supported). Possible solutions could be a) tile the console where each part shows the output of a chosen process b) present the chosen processes in the same console (with different fonts and/or colors) a) probably complicated to implement while b) is relative close to what you suggest in 7715: if the process list would allow multiple selection.
marking as later (until 2.1 feature set is determined).
To consider with console consolidation in 3.0. If we have a tabbed pane of consoles, we should consider the ability to layout the tabs, as in the editor pane.
Deferred. The console is a page book view. Currently the workbench does not support a tabbed presentation of page books.
*** Bug 64126 has been marked as a duplicate of this bug. ***
Re-open for 3.1. Consider use of workbench feature to open more that one view of the same type in a perspective.
*** Bug 74524 has been marked as a duplicate of this bug. ***
Need to investigate ways we can present multiple consoles at once.
We can open a second console view in the same perspective using the IWorkbenchPage.showView(String viewId, String secondaryId, int mode), however this is not the method called by default when a user chooses console view from the Window/Show View method. Doug is there any way to make that menu item create a new view every time instead of activating an existing view?
We could, but I don't believe this is the behaviour we want by default. I'm not sure how we would could about doing this without (a) cluttering the user interface; or (b) confusing the user.
Which part do you think would be confusing/undesirable? Having more than one console view, or using the Show View action to open them? How else can we display more than one console at once?
It might work to add a tool bar item to your console view (or context menu, or view menu). In the purely naive case, you have two items for each view or two menus: "show view", "show view again". What do you propose? From my perspective (perhaps naive), this seems like something that is a specific problem for the console view. Do you feel it's a more general problem?
I agree with Doug's comment 18: the default should be as is. Maybe we could specify this in the launch configuration, something like "Open in new console".
I think the user needs to be able to do this from the console view itself. For example, the user may want to see the CVS console seperately from process consoles. In this case, there is no launch configuration.
Fixed in console plugin. Used a console factory to create new Console views. All views contain all consoles. Users can use the "Pin Console" independently in each console view to view different consoles in each view. Changes: * IConsoleConstants - removed P_AUTO_SCROLL * IConsoleView - added setScrollLock() and getScrollLock() * TextConsole - removed fAutoScroll, getAutoScroll(), deprecated setAutoScroll(...) so as not to cause compile errors in CVS Console. Method is a no-op now, but Scroll lock is off by default so behavior doesn't change for CVS Console. * ConsoleViewConsoleFactory - new class * ConsoleManager - changed showConsoleView(IConsole) to show the console in all console views. * ConsoleMessages.properties * ConsoleView - implemented new methods in IConsoleView. showPageRec(..) updates the state of scroll lock action on Console Pages. * IInternalConsoleConstants - removed PREF_CONSOLE_SCROLL_LOCK * IOConsolePage - no longer listens for PREF_CONSOLE_SCROLL_LOCK changes. * PinConsoleAction - updated * ScrollLockAction - updated * plugin.properties * plugin.xml - added new ConsoleFactory extension
Darin W, please verify
Verified. Filed bug 80719 and bug 80720.
