But whatever works for you is fine
This is the background of it all:
https://www.dropbox.com/s/zp6rsqktc0uu8jt/20201211_094700.jpg?dl=0You can see, first I used classes and ports to (wrongly) use them to show important call stacks in my software.
Now when I try to use proper UML syntax for call stacks by using objects, actions and dependencies of stereotype <<call>> you can see it all becomes quite space-consuming and hard to create. You know, it's just a part of the actual diagram which actually shows the survey for all 15 main objects we have in the core software, and how the control flow via the main calls is wired. I wish there was more support for such stuff which is essential for software modelling, because I have the patience but my team mates have not. They refuse UML because it's all so complicated to
fastly create a diagram e.g. showing how objects are wired with important calls. ...And it takes so much space now while it could be smaller if you look at my first attempt which is the upper diagram.
(P.S.: The object "ProcessingFinished" in the lower diagram is actually a sub-object, and two such objects are connected with a signal-slot call mechanism. "Enqueue" is a method of the base class of the object.
BTW: Another big issue with Sparx EA is the problem that I have to manually rename actions if I rename methods and attributes of classes in the model tree. Actually a killer if one has 20 diagrams and has to refactor all UML actions after renaming class methods.)