This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 153361 - Open edit box when inserting model elements
Summary: Open edit box when inserting model elements
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: General (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-18 09:23 UTC by thomasmatzner
Modified: 2008-11-18 09:39 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thomasmatzner 2008-11-18 09:23:47 UTC
When inserting attributes and methods in the project tree, right-clicking a class and choosing "New
Attribute/Operation", a new element is inserted, given the name "Unnamed", and the type int (if attribute) or void (if
operation). In most cases this is not what the user wants, so the next step is to right-click the thing and open
Properties, to enter a meaningful name and probably more documentation. So why not opening the editing box for the newly
created element immediately on its creation?
Comment 1 Sergey Petrov 2008-11-18 09:31:54 UTC
thanks for your feedback.
I have properties window usually opened by default, but it's not the solution.
as for project tree, only name change is supported, you can change it from project tree by double click (with delay
between clicks) or by F2 pressing.
If you add attribute/operation on a diagram you can press Enter and correct type, visibility, name, parameters in inline
editor.
Comment 2 thomasmatzner 2008-11-18 09:39:34 UTC
Thanks Sergey, obviously I didn't make quite clear what I suggest. If I want to edit more than the name (which I have to
edit anyway), I can open the properties box from the project tree. My suggestion is that it opens automagically when
inserting from the project tree. That would make sense in particular in the project tree, as no further modifications
(types, parameters) are possible from the tree.