Bug 240169

Summary:	Debug toolview not removing ouput views when clicking on close button
Product:	[Applications] kdevelop	Reporter:	Victor Vicente de Carvalho <victor.v.carvalho>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	victor.v.carvalho
Priority:	NOR
Version:	4.0.0
Target Milestone:	4.0.1
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Victor Vicente de Carvalho 2010-05-31 04:33:21 UTC

Version:           4.0.0 (using KDE 4.4.3) 
OS:                Linux

When debugging an application, an outputview (for program standard output) is created for each run instance. When clicking on "close the active output view" the view is closed correctly. But when starting the debugger again it reappears magically. This happens on all windows that a are closed.

And, as a wish, a "close all" button should be useful, or something automatic closing the view when a new debug instance starts.

Reproducible: Always

Steps to Reproduce:
Debug a program. The outputview appears and works as spected. Stop debugging. Close the view (clicking on the close button on the right side of the view). The window closes as spected. Now start debugging again.

Actual Results:  
All closed windows reappears like they were just hidden, not closed.

Expected Results:  
The closed windows should be really closed.

Comment 1 Andreas Pakulat 2010-05-31 12:06:16 UTC

Is this maybe because when starting to debug KDevelop switches to the Debug area? Each area has its own set of toolviews and hence closing the output window in the Code area doesn't do anything to the output window in the Debug area, you have to close it there too if you want it to vanish.

Comment 2 Victor Vicente de Carvalho 2010-05-31 14:54:18 UTC

Hummm, saw that now. This behaviour is not a bit... unexpected? At least the debug toolview should not appear on code area, or the two should be synced together when the user closes a output window? There are uses for the debug toolview when on code mode?

Comment 3 Andreas Pakulat 2010-05-31 15:31:02 UTC

Thanks for confirming. This is the intended behaviour actually.