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 138715 - State shape persists after diagram closed
Summary: State shape persists after diagram closed
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram State (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-01 14:45 UTC by rsearjeant
Modified: 2008-07-31 21:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
State shape persistence (37.74 KB, image/jpeg)
2008-07-01 14:47 UTC, rsearjeant 		Details
State shape persistence (2) (24.21 KB, image/jpeg)
2008-07-01 14:48 UTC, rsearjeant 		Details
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 rsearjeant 2008-07-01 14:45:18 UTC 
My Environment:

Product Version: NetBeans IDE 6.1 (Build 200804211638)
Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22
System: Windows XP version 5.1 running on x86; Cp1252; en_GB (nb)

Steps to reproduce:

1) Create UML project
2) Create a new state diagram
3) Add some states to the new diagram
4) Double-click a state to edit its label
5) Without completing the edit, either close the diagram or navigate to another tab (e.g. a code window)
6) The state shape, complete with text cursor, remains rendered on top of whatever other window you open.

See attached screenshots.  I found that sometimes I could use the escape key to cancel the edit, but this doesn't always
work for me and only quitting and restarting NetBeans will fix it.
Comment 1 rsearjeant 2008-07-01 14:47:47 UTC 
Created attachment 63760 [details]
State shape persistence
Comment 2 rsearjeant 2008-07-01 14:48:24 UTC 
Created attachment 63761 [details]
State shape persistence (2)
Comment 3 Peter Lam 2008-07-07 20:00:50 UTC 
This problem has been fixed in NB 6.5.
Comment 4 Peter Lam 2008-07-31 21:34:53 UTC 
verified in NB 6.5 UML daily build 20080731