Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - PeterHeintz

Pages: 1 ... 35 36 [37] 38 39 ... 47
Don’t be so grounchy! :) :) :)

Well, that indicator is uml standard and I found an example on page 202 showing the intention as I use it.

It is not the association direction (if any), it is the direction of the label (how it should be read).
And label is label on whatever diagram it is.

Yes, that's my impression as well.

I use connector direction to provide reading directions for users.
“Car” “has” “Engine” were the direction from “has” goes from Car to Engine to ensure that the user does not read “Engine” has “Car”.

However this direction is not bound to the connector but to the connector on a diagram.
In other words each time I use the connector in an other diagram I have to set the direction anew.

I thing binding the direction to the connector only should be there.
Is there a sense in that current implementation or is that just a wrong implementation? :-\

Any opinions?

I have posted a feature request several months ago.
The simple solution from my perspective would be to access tagged values as reporting constants of the root package in the same way as possible in the package processing within the templates.

How did you generate the epf xmi?

General Board / Re: Integration with Eclipse Modelling
« on: May 20, 2016, 04:23:56 pm »
There is this one:
But to be honest, I tried to get it work but did not managed in my short time I had.
I assume that it works for pure UML, once the environment runs.

This is what I assumed, but I had some hope.
I still have the problem of having some meta data I need to put on cover page, header, footer which are on package level but I cannot cover with reporting constants.
Any idea on that, rather than duplication templates?

General Board / Re: mts files ModelTemplates section handling
« on: May 20, 2016, 04:11:49 pm »
Thank you!

General Board / Re: Migrating from SysML1.3 to 1.4
« on: May 20, 2016, 04:07:21 pm »
Thank you!
I will stay on V1.3 and wait.
Once it is available and you need a beta user please let me know.

Greet, which tagged values?
Tagged values I define in the virtual document package myself?
Can I define and use a tagged value of “mySpecialTag” and use it e.g. in headers and footers?

General Board / Re: Migrating from SysML1.3 to 1.4
« on: May 20, 2016, 02:43:53 am »
I would appreciate response from Sparx!
Thank you!

Suggestions and Requests / Re: Security: revert to own user
« on: May 20, 2016, 12:43:24 am »

On the history page for V12.1
I found following:
Specify ReportAuthor, ReportTitle, ReportName, ReportVersion, ReportStatus and ReportAlias by adding tagged values to the generated package

But what does it mean?
Using package attributes like ReportAuthor, ReportTitle, ReportName, ReportVersion, ReportStatus and ReportAlias as report constants was already there in Vxx <V12.1.

Does it mean that I can now specify my own tagged values as reporting constants, and if so how do I use them in a document template?

General Board / Migrating from SysML1.3 to 1.4
« on: May 20, 2016, 12:29:08 am »
I now switched to V12.1 and by that, I want to switch my models from SysML 1.3 to SysML 1.4 as well.

There are not many differences between 1.3 and 1.4 but some exist e.g. the unit and quantity kind are now no longer stereotypes but instance specification.

Do I just have to change the type of the diagrams from SysML 1.3 to 1.4, or do I have to consider something else.

Is there anyone who could give me assistance?

Pages: 1 ... 35 36 [37] 38 39 ... 47