Invisible elements in a diagram, cannot assign classifier

111 views
Skip to first unread message

Paul Corbett

unread,
Feb 2, 2016, 11:43:10 AM2/2/16
to StarUML
First off, I screwed up.

I reversed several directories in my project which did not place the elements in the correct packages. I move things around, but had duplicates and did know how to merge elements of the same type

Made the diagram in the screen shots

Later I deleted the packages made by the reversing. Apparently, one element referenced in the diagram was to an element in these packages.

Now, the next day, there are invisible elements on the diagram. They are still there, because I can select them. When you look at the properties, the classifier is empty. I tried to assign the correct classifier, but the program will not accept it.

Also, got an error trying to enable node debugger (see 4th screen shot).

1) If there is a reference to an element and the element does not exist, then the reference should be removed or the program should allow the user to assign a new reference.
2) An element in a diagram should never be invisible. If there is a problem then the program should display some kind image denoting the problem and provide a path for the user to correct it.
Screenshot from 2016-02-02 10:20:10.png
Screenshot from 2016-02-02 10:20:42.png
Screenshot from 2016-02-02 10:20:53.png
Screenshot from 2016-02-02 10:39:17.png

StarUML

unread,
Feb 2, 2016, 10:09:13 PM2/2/16
to StarUML
Hi Paul,

It looks very exceptional situation because invisible elements are not allowed in StarUML. We recommend to delete the invisible elements and create them again.

And, we need to figure out how the invisible elements were created. To do that, we have to find the correct steps to reproduce the invisible elements. If you know how to reproduce, please let us know or if you don't know, then please share the followings:

- Your file (.mdj)
- The source code you reversed (C/C++, Java, or C#?)
- StarUML version and the version of the extension you used to reverse.

Sending the above to our email (sup...@staruml.io) is ok.

Thanks,
StarUML Team

2016년 2월 3일 수요일 오전 1시 43분 10초 UTC+9, Paul Corbett 님의 말:

Paul Corbett

unread,
Feb 3, 2016, 8:43:44 AM2/3/16
to StarUML, sta...@googlegroups.com
1) Create new project
2) Add a class
3) Add an object diagram
4) Created instance of class on object diagram
5) Delete the class
6) Save the project
7) Open the project
8) View the object diagram; it should be empty. 
9) View the properties of the instance; looks like a classifier has not been assigned
10) Preform a board select in the object diagram. Selection outline of invisible instance will appear
11) Add another class to the project
12) Assign the new class as the classifier of the instance; looks like it accepts it, but click on something else then go back and see that the classifier looks like it is not assigned

Hope this help.

StarUML

unread,
Feb 4, 2016, 3:03:00 AM2/4/16
to StarUML
Thank you for sharing detailed steps to reproduce.
We've found a bug that object view becomes invisible when corresponding class is deleted. Because of this bug, assigning classifier is not work.
We will fix this bug in the next minor release.

Thanks,
StarUML Team

2016년 2월 3일 수요일 오후 10시 43분 44초 UTC+9, Paul Corbett 님의 말:

StarUML

unread,
Apr 20, 2016, 9:02:19 AM4/20/16
to StarUML, sta...@googlegroups.com
Now fixed in version 2.7.0

Thanks,
StarUML Team

2016년 2월 4일 목요일 오후 5시 3분 0초 UTC+9, StarUML 님의 말:
Reply all
Reply to author
Forward
0 new messages