280828 – Undo/Redo/Paste problems in manifest editor

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 280828 - Undo/Redo/Paste problems in manifest editor

Summary: Undo/Redo/Paste problems in manifest editor

Status:	RESOLVED DUPLICATE of bug 68423

Alias:	None

Product:	PDE
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.5
Hardware:	PC Windows Vista

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	PDE-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-06-18 16:06 EDT by Wim Jongman
Modified:	2009-06-18 18:10 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Wim Jongman

2009-06-18 16:06:19 EDT

The manifest editor now allows CTRL+Z and CTRL+Y to redo and undo. However, I have experienced problems to such an extend that I had to restore from local history due to a misformed plugin.xml. 

I cannot duplicate as of yet but it seems important enough to make a note. 

A problem that can be duplicated in the manifest editor is the following (related?) scenario.

In the extension tree I CTRL+X a tree item.
I click on another item and type text in the attribute area on the right
then I don't want this text and press CTRL+Z.
instead of undo of my last typed words i get an undo in the extension tree.

I will keep trying to duplicate the misformed plugin.xml problem and log that in a seperate bug


-- Configuration Details --
Product: Eclipse SDK 3.5.0.v200906051444 (org.eclipse.sdk.ide)
Installed Features:
 org.eclipse.pde 3.5.0.v20090123-7Z7_F8NFE-z0VXhWit08PbD5

Comment 1 Benjamin Cabé

2009-06-18 16:36:27 EDT

This is pretty bad, we know that, and we'll certainly try to improve the undo/redo handling in 3.6.
Anyways, thanks for taking time for reporting the bug, Wim.

*** This bug has been marked as a duplicate of bug 68423 ***

Comment 2 Wim Jongman

2009-06-18 18:10:55 EDT

I actually searched for this bug but I could not find it for 3.5...