Version: 1.5.1 (using KDE 3.5.0, Debian Package 4:3.5.0-3 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.12-1-686 When adding a new attribute to an entity in 'entity attributes' tab of 'entity properties' dialog, recently added attributes are displayed incorrectly in a list of attributes. After reopen of the dialog, all entities are displayed correctly. Sanity check: 1. Create new ER diagram. 2. Create new entity (say "A"). 3. Open its 'Properties' dialog and select 'Entity Attributes' tab. 4. Press 'New Entity Attribute...' 4. Select attribute type 'blob'. 5. Type attribute name 'logo'. 6. Press 'OK' and see that there is "blob" entry appeared in attribute list instead of correct "logo:blob". 7. Close dialog pressing 'OK'. 8. Open the dialog again. 9. Switch to 'Entity Attributes' tab and see that "logo:blob" is displayed -- so re-open is a workaround. 9. Press 'New Entity Attribute...' 10. Leave attribute type as 'int' 11. Type in attribute name 'foo' 12. Press 'OK' and see that "foo" entry has been added to the attribute list instead of "foo:int". 13. Close dialog. 14. Press undo (Ctrl-Z) and see that attribute names in a 'UML Model' frame became strange: "logo:100" and "foo:82". So, three bugs in one shot. Ouch... Is there any way to obtain CVS sources? Maybe I can fix some bugs.
> Is there any way to obtain CVS sources? Maybe I can fix some bugs. Hey, great! It's Subversion these days, See http://developer.kde.org/documentation/other/developer-faq.html#q1.8
SVN commit 508487 by okellogg: Set entity attributes to work. BUG:120742 BUG:120750 M +16 -8 associationwidget.cpp M +3 -7 attribute.h M +5 -3 classifier.h M +6 -3 dialogs/classifierlistpage.cpp M +16 -6 entity.cpp M +10 -6 entity.h M +15 -86 entityattribute.cpp M +10 -26 entityattribute.h M +15 -1 listpopupmenu.cpp M +12 -0 model_utils.cpp M +5 -0 model_utils.h M +2 -8 object_factory.cpp M +60 -29 umllistview.cpp M +13 -11 umllistviewitem.cpp M +4 -0 umlobject.cpp M +7 -0 umlobject.h
*** Bug 113499 has been marked as a duplicate of this bug. ***
*** Bug 124275 has been marked as a duplicate of this bug. ***