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 82974 - tag value like {=,=,=} is displayed in the class element
Summary: tag value like {=,=,=} is displayed in the class element
Status: RESOLVED INVALID
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Class (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-18 12:51 UTC by Andrew Korostelev
Modified: 2008-05-14 21:45 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 Andrew Korostelev 2006-08-18 12:51:58 UTC
Pressing Add button on the Tag Value dialog without entering any value will
display {=} in the class element on the diagram.

Repro steps:
- create a uml project
- create a class diagram
- create and name a class element
- from the properties for the class element, click on the "..." button for the
Tag Values to bring up the Tag Values dialog
- press the Add button a few times
- press the OK button
Result: {=,=,=} is displayed as tag value in the class element. one "=" for each
empty value.
Comment 1 George Vasick 2007-05-17 18:43:05 UTC
Planned for drawing area upgrade after NB 6.0.
Comment 2 George Vasick 2007-05-18 00:34:11 UTC
Should not use resolved/later status.
Comment 3 George Vasick 2007-06-28 22:51:03 UTC
Targeted in drawing area redesign.
Comment 4 George Vasick 2007-07-04 00:56:07 UTC
Restoring original priority and using the standard NB waiver process.
Comment 5 George Vasick 2008-01-02 17:47:26 UTC
Diagram area bugs waived for 6.0 will also be waived for 6.1.
Comment 6 Trey Spiva 2008-05-14 21:42:53 UTC
What should we do.  The nodes are showing the data.  The user added tagged values, but did not set the name and value.  Therefore the diagram displays 
the correct data.  This is a case of bad data.
Comment 7 Trey Spiva 2008-05-14 21:45:32 UTC
I also think that this is a very low use case.  It should be a p4 at best.  The data is not corrupted.  It is simply user error.