marek-piirikivi

@sz332 I think utilizing property page space for multiselection options makes sense. This area shows options/details about a single selection. I think it should do so with multiselection as well....

I did some reading within UML specification and it proposes both versions - so pin's seems to be optional :thinking: So, it might be not possible to automatically enforce the...

@sz332 I agree. I have never seen an object flow without pin. However; seems like the standard does not care. I have not checked SysML standard yet - it generally...

I have a proposal. Everything stays as is; but then you have just created a flow to the activity which is not connected to the pins; a small floating button...

A workaround is to create separate swimlanes with "Partitions" number as 1. Looks the same, you get the benefit of individually scaling a partition, and querying works as expected ....

I'll confirm this later. If I do not see the problem anymore, then I'll close the issue.

I have not implemented anything related to primitive types yet. For the first version I am implicitly assuming that all the values are Real values.

The problem seems to be with actions, activities etc as well. I was able to form refine relationship only between a requirement and a block.

That's rough problem to solve automatically. I remember @sz332 proposed somewhere to make the names draggable so you can reposition them more freely. Maybe we want to pursue this?

Thank you for drawing attention to that. This would definitely be a fine addition. If you want to get started with this on your own, few pointers to get you...