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 95187 - Composite State element name can't be handled by mouse
Summary: Composite State element name can't be handled by mouse
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram State (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Viktor Lapitski
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2007-02-12 06:56 UTC by Peter Lam
Modified: 2007-02-22 20:15 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lam 2007-02-12 06:56:13 UTC
This is a regression. There are 2 issues here but they might be related so put
them all here.

1. After typing in the name and press Enter, Unnamed is displayed as the name of
the element and in the properties window. It's actually naming the 1st column or
row after column or row are added to be visible. 
2. Double clicking on the element name would not put the name in the edit mode
either.

Repro steps:
- create a state diagram
- create Composite State element in the diagram
- enter a name by selecting the element if not yet selected and press Enter 

Workaround: rename element from project tree or properties window
Comment 1 Viktor Lapitski 2007-02-12 13:36:34 UTC
The part 1 happens to be fixed as 95188.

Part 2 doesn't look like a regression - i checked on some 
almost month old build (before the series of the fixes related 
to handling of non-ascii chars), and the bug was there. Anyway, 
considering that after the fix mentioned above the element name 
can be traversed to and edited using keyboard i downgrade the bug.
Comment 2 George Vasick 2007-02-12 16:12:49 UTC
Per Peter, this is a regression compared to Coco.
Comment 3 Peter Lam 2007-02-12 16:46:49 UTC
correct. we're comparing to coco (jse 8.1) as the base to say if a bug is a
regression, not compare to previous builds. 
Since there's viable workaround, leaving it for CA release is ok but it should
be fixed for FCS release.
Comment 4 Viktor Lapitski 2007-02-17 06:26:32 UTC
fixed in release55 branch.
Comment 5 Peter Lam 2007-02-22 20:15:32 UTC
verified build 070222.