Version: 1.5.7 (using KDE KDE 3.5.2) Installed from: Compiled From Sources OS: Linux when creating a state diagram, i have class that appears in the tree view. An e xample is a class with name: EjHpBSYmKbd1. If i search this name in the xmi, i find : <UML:Class isSpecification="false" isLeaf="false" visibility="public" namespace="1" xmi.id="wMX2epCB8sdp" isRoot="false" isAbstract="false" name="EjHpBSYmKbd1" /> the xmi.id points to : <UML:AssociationEnd isSpecification="false" visibility="public" changeability="changeable" isNavigable="true" xmi.id="2485" aggregation="composite" type="wMX2epCB8sdp" name="" /> and <UML:AssociationEnd comment="une fiche affiche une demande de devis " isSpecification="false" visibility="public" changeability="changeable" isNavigable="true" xmi.id="3073" aggregation="none" type="wMX2epCB8sdp" name="" multiplicity="1" /> the above line is an association end of an association in a class diagram.
Created attachment 20483 [details] the xmi file yes ;-) i found the way to attach my xmi
Cannot confirm using branches/KDE/3.5/kdesdk r661855. Started with an empty model, created a state diagram with a start and end state and a few forks/joins, states, and state transitions. Saved it to file, loaded it back successfully.
I think this is related: http://bugs.kde.org/show_bug.cgi?id=142039 and I also had problems, opening file from earlier version in an 1-2 months old (when I tried) SVN version. Class like that appeared (in class diagram), I deleted, worked on the file, and class appeared again (and again and again) when opening the file again. I kept on deleting it. Similar names like mentioned in these two reports. If needed, I can send the file in e-mail, but first I'll have to try the current SVN. I think it depends on something from the old file (but random named class was not visible in the old public release). So I am not sure you can reproduce this by using only the current version and creating new diagram in it... you may need an old file.
I believe this is fixed, see bug 145709. Just to make sure, could you check again with current SVN?
*** This bug has been marked as a duplicate of 145709 ***