Bug 30790 - [Schema Editor] Not obvious how to rename an attribute
Summary: [Schema Editor] Not obvious how to rename an attribute
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2   Edit
Assignee: Dejan Glozic CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2003-02-02 23:48 EST by Nick Edgar CLA
Modified: 2006-06-21 02:04 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2003-02-02 23:48:30 EST
 
Comment 1 Nick Edgar CLA 2003-02-02 23:52:59 EST
build I20030115

In the schema editor, when I create a new attribute, it gives it a default 
name.  I then have to rename it.  

It's not obvious how to do this.  I eventually figured out that you have to 
right click, choose Properties, select the name in the Properties view, and 
type the new name.

Fixing bug 30789 would help, but it could still be improved.

Some options, in order of preference:
1. Support in-place rename in the editor itself.  Add Rename... to the context 
menu, and hook the global action.  Invoke this automatically when creating a 
new attribute (or element).

2. Prompt for the new name when creating a new attribute (or element).

3. Automatically activate the Properties view, with the name selected and its 
cell editor active.  Add Rename... to the context menu, and hook the global 
action.  Invoke this automatically when creating a new attribute (or element).
Comment 2 Dejan Glozic CLA 2003-03-02 19:57:36 EST
For now, we will only fix bug 30789. While using schema editor, changing the 
name property is not the only change need, so coming up with a special renaming 
mechanism doesn't seem right when property sheet will be needed anyway.
Comment 3 Wassim Melhem CLA 2006-06-21 02:03:33 EDT
ancient history.
Comment 4 Wassim Melhem CLA 2006-06-21 02:04:13 EDT
no longer an issue with the new schema editor.