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] 2 3 ... 53
Bugs and Issues / Stereotype Dialog is Faulty
« on: June 18, 2019, 09:40:52 pm »
The new stereotype dialog introduced in V14 seem to intend to address a better filtering of many stereotypes. However now setting stereotypes is more often a complex or even impossible search.
Example: In V14 in tried to change an object in an SysML activity diagram to a <<datastore>>, but I had to go to UML instead of SysML1.5 to do that. In build 1503 even in UML the <<datastore>> has gone. I have no idea how I can set my object to be a <<datastore>> in build 1503.

Please validate what is shown in the stereotype list associated to a Perspective/Profile.
Currently it is more or less useless.

Seen in build 1428
The behaviour of an action is not shown in the diagram if the “Show Behaviour in Diagram” checkbox is checked.

Bugs and Issues / V15Beta Behaviour Properties Dialog Lost
« on: June 06, 2019, 08:41:10 pm »
When you double click e.g. on a “do” behaviour of an action in V14 the “Behaviour Properties” dialog opens. In build 1503 nothing happens.

It is possible to define the compartment visibility either on diagram level or on element level. Former times, element level definition had highest priority (what makes sense). Not it seems that diagram level has highest priority (makes no sence).

Several Label like pin name are not resizable to have multiple lines anymore!

Bugs and Issues / Activity Frame; Useless Auto Horizontal Resize
« on: June 05, 2019, 07:07:45 pm »
Seen in Build 1502

In a SysML activity diagram the diagram frame is made bigger in size each time something on the diagram is repositioned in any direction.

Seen in Build 1502 and 1428!

I tried to reduce the height of a SysML state machine frame, having concurrent state regions, a little bit. This caused the concurrent state regions repositioned vertically in a way that the states are not anymore in the right regions. Even worse the regions moved down and finally this diagram frame was higher in size rather than smaller. Each try to fix that, caused the regions to go deeper and deeper and the diagram frame height became higher and higher.

So I tried to fix that, with build 1428, but at the end I got a diagram frame covering over 50 pages in height.

The only way to get that fixed, was using V13, however moving 6 concurrent state regions over 50 pages up is really a imposition.

Bugs and Issues / Diagram Frame SysML IBD Ports are Wrong Placed
« on: May 30, 2019, 12:49:23 am »
When IBD is show in another diagram as diagram frame the ports within the IDB are not shown correctly on the block border but within the block.

Seen in Build 1428 and higher.

Bugs and Issues / Wrong content shown in „Connector Notes“
« on: April 29, 2019, 09:57:07 pm »
When you call a message in a classified lifeline within sequence diagrams and you give that message connector a note, the following problem occurs:

Within the Connector Properties”/Notes all works well, but if you look in the “Connector Notes“ the note of the lifeline classifier is shown.

General Board / Re: Template selector based on package name
« on: April 16, 2019, 10:13:36 pm »
No, this is not supported (unfortunately)

General Board / Re: Search criteria for all users Repository
« on: April 12, 2019, 11:36:26 pm »
You can use the MDG to publish your queries

This plan I had as well.
For V14 I am not 100% sure, but I let a student of mine check it, and he stated that the API still misses the features needed.

API can currently not be used as a work around. I inserted a similar post some time ago.

There is no api feature like getPackagePath. However you can use the api to crawl through the packages and element to build you own getPathFeature.

Uml Process / Re: Check In/Out if nothing has changed on the model
« on: March 28, 2019, 10:12:14 pm »
Yes, using SVN is a kind of overhead.
In our environment we typically use just MS-SQL DB without an external version control system as long as possible.
If we really need to compare or revert old stuff with new stuff, we use the Package Baseline feature. Later maybe when the stuff goes to maintenance we switch to SVN.
This does not mean that you should do the same, but you should not just handle model elements as your users handle source code without thinking.

Pages: [1] 2 3 ... 53