Bug 193149

Summary:	[Scratchpad] Remote Scratchpad not Cleared when closing view
Product:	[Tools] Target Management	Reporter:	Kevin Doyle <kjdoyle>
Component:	RSE	Assignee:	David Dykstal <ddykstal.eclipse>
Status:	RESOLVED INVALID	QA Contact:	Martin Oberhuber <mober.at+eclipse>
Severity:	trivial
Priority:	P4	CC:	dmcknigh, kmunir
Version:	2.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	194899

Description Kevin Doyle

2007-06-18 13:32:36 EDT

If you drag and drop something into the Scratchpad and then close the view and reopen it, the old contents are still visible.  Since we don't save the contents when closing the workbench the contents shouldn't be saved when closing the view.

-----------Enter bugs above this line-----------
TM 2.0RC3 Testing
installation : eclipse-SDK-3.3RC4
RSE install  : RSE 2.0 RC3
java.runtime : Sun 1.5.0_11-b03
os.name:     : Windows XP, Service Pack 2
------------------------------------------------

Comment 1 Martin Oberhuber

2007-06-28 09:03:43 EDT

I cannot follow the argument.

Changing perspectives also makes the Scratchpad invisible, but you'd expect its contents to remain there. So I cannot see why closing it should get rid of its contents.

MS Office also has a Clipboard Viewer, and closing it does not delete the contents of the clipboard. Similarly, closing a Properties View does not get rid of the Properties. I'd tend to mark this WONTFIX unless Kevin chooses to mark it INVALID or we have other opinions. Dave's?

Comment 2 Kevin Doyle

2007-06-28 10:05:55 EDT

I'm marking this INVALID as per Martin's comments.  

My main reason for opening this is because of how buggy the scratchpad is right now.  You can run into case's where you need to reset the scratchpad and if closing and reopening it doesn't do that then the user needs to restart the workbench.

Comment 3 Martin Oberhuber

2007-06-29 07:17:43 EDT

(In reply to comment #2)
> My main reason for opening this is because of how buggy the scratchpad is right
> now.  You can run into case's where you need to reset the scratchpad and if

Ok, I see your point. I think a better solution for this is to beef up the existing scratchpad's "Remove All" toolbar action such that the entire scratchpad is reset. I filed bug #194899 asking for this.