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 4 ... 58
In earlier V14 versions there was an element hopping from parent to parent when elements are dropped to a diagram, which was removed in later V14 versions.
This element hopping from parent to parent is now back again. :'(
A frequent scenario I have is, when using “send signal” and “accept event” actions (SysML). To find out, what send signals are accepted by which action in different activities I put a trace dependency between both actions.
To show this trace in a diagram, I put corresponding action into the subtend diagram. Before V13 I put the “traced action” outside of the frame, to make clear that this action does not belong to the activity shown in the diagram.
Since V14 putting something outside the frame was not allowed anymore. So since V14 those “trace actions” are inside of the activity frame.

What I want to express, are relations of an action in one activity to actions in another activity by traces.
Now in 1551 my actions change its parent again, but even worse as before. When I drop the “foreign action” in my diagram and after creating the trace, the foreign action remains in its original parent. However after moving the “foreign action” within that diagram to another position, the parent of the “foreign action” becomes the parent activity of the diagram.

At least in SysML models moving to newer EA versions recently causes to corrupt the diagram layout frequently. So I will have to fiddle around with element positions and this will cause to move my actions to other parents and I have a lot.
All this is really annoying! >:( >:( >:(

Hi Eve,
For me it was not a feature confusion.
I had the problem, that one of our Admins has used the “Required MDG Technologies” functions for technologies which are stored within the model.
This leaded direct or maybe later to the condition that nobody could open the model (neither V13, V14, V15) because of missed but “model stored technologies”!?
With “nobody could open the model” I really mean nobody. This is because all users (accept the one and only Admin account) use Windows Authentication in our repository and those could not login. Therefore also the non-Windows account admin could not login, because EA cannot be forced to provide a login dialog if Windows Authentication is enabled before a windows login took place.

Even if the “Required MDG Technologies” feature work properly this scenario could happen.

From my perspective I recommend:
Allow to login users readonly if the required technologies are not there or,
 introducing an EA feature which allow to login (not switch), without Windows Authentication even if Windows Authentication is enabled or,
give a hint in the user manual, that if the “Required MDG Technologies” together with enabled Windows Authentication is used at least one Windows account should have admin rights

Yes, that was what I assumed as well!
But it worked! After disabling the windows login I could login as admin and uncheck the mdgs required.
The strange thing left is, that all mdgs are in the model, so they were there!?!?

Hi Geert,
Thank you!
I already found the table.
Currently I intent to disable windows authentication on SQL level, to find out if at lease the admin is allowed to login even with missed mdgs.

Bugs and Issues / Cannot access my model due to missed technologies
« on: June 05, 2020, 02:09:05 am »
When I try to access my repository, I get the following message:
Access to the model requires following technologies which are not available:

So it seems that an “Admin” has marked some MDGs as required.
I assume that the MDGs are model MDGs so this message should not occur anyway.
I have the hope that an admin can login to fix that problem.
Apart of the admin account all users use Windows Authentication.
I have the password of this one and only non-windows admin account, but how can I login as admin without the need to first login with my windows account which do not work?

An integrity check of my repository shows the problems below.
 A Recover/Clean causes EA to crash silently.
This problem I see in several V14/V15 builds.
Any idea?
| Integrity Check Report.
| Generated: Mittwoch, 03 Juni, 2020
| No. Items: 10
1 - Link geometry. ITEM: Duplicate Link Information. ACTION: Delete duplicate Link Geometry.
2 - Link geometry. ITEM: Duplicate Link Information. ACTION: Delete duplicate Link Geometry.
3 - Invalid link geometry. ITEM: Missing Diagram  . ACTION: Delete Invalid Link Geometry.
4 - Invalid link geometry. ITEM: Missing Diagram  . ACTION: Delete Invalid Link Geometry.
5 - Invalid link geometry. ITEM: Missing Diagram  . ACTION: Delete Invalid Link Geometry.
6 - Invalid link geometry. ITEM: Missing Diagram  . ACTION: Delete Invalid Link Geometry.
7 - Invalid link geometry. ITEM: Missing Diagram  . ACTION: Delete Invalid Link Geometry.
8 - Invalid connector. ITEM: Association. ACTION: Delete Connector.
9 - Invalid connector. ITEM: Association. ACTION: Delete Connector.
10 - Invalid connector. ITEM: Aggregation. ACTION: Delete Connector.

Well, the thing is, that the update script provided by sparx did not update that old lib stuff entirely.
Within V14 there was not problem about that and at the end there is no difference between SysML1.3 InterfaceBocks and SysML1.4/SysML1.5 InterfaceBocks.

I considered to do the SysML1.3 bulk update myself, but it is not easy to do that, when you want to use SysML1.5 but according whatever rule some elements you have to update to SysML1.4 and not to SysML1.5 ::).

A search leads just to an empty list and the browse shows packages but no elements.
The text box which might represent the filter you have mentioned shows:
Types : 'Class'
Stereotypes : SysML1.4::InterfaceBlock

What I what to classify has a stereotype Types : SysML1.5::ProxyPort and my classifier has the stereotype SysML1.3::InterfaceBlock.
Currently if you create new things for SysML1.5 some gets "SysML1.5." and some gets SysML1.4 for whatever reason.
My SysML1.3::InterfaceBlock is from an old library.

Do you know how I can change this filter?

Neither Browse not Search delivers classifiers which can be used to set the type.

In V15 versions the content of my generated documents is scaled down. What looks fine in any former EA version is somehow scaled down round about to 75% (75% usage of my page size).

Bugs and Issues / Report generation order lost
« on: May 11, 2020, 11:21:02 pm »
When I generate a report, sometimes the sequence of the items (packages, elements) is mixed up.
It seems to me, that the sequence gets sometimes wrong when I start the document generation after I have modeled a longer time and that the sequence is always right when I start the document generation direct after opening the repository.

(seen in 1428 and several other builds)

Bugs and Issues / Unmotivated line breaks of text in diagrams.
« on: May 11, 2020, 11:19:25 pm »
Mainly e.g. on names of ports and pins I have the problem that text show, gets line breaks frequently. Having that detected I change the text box size in a way the diagram is readable, but later I will get the line breaks again.

This is a real annoying Sisyphus situation. For me it seems that document generation is at least one source causing this nightmare.

After document generation, I saw some unmotivated line beaks in the report but not in the diagram and some in both the report and the diagram.
What I also see is a growth of this unmotivated line breaks over the time.
At the end several of my diagrams corrode over the time to be unreadable at the end.
(seen in 1428 and several other builds)

Yes, what you describe is really a problem in newer EA versions!!!

In V14 or V15  (I do not remember) Sparx programmed some magic but senseless assumptions when you drag and drop something related to activities.
Most of those silly features disappear in V15.1 but some might buzz around.

General Board / Re: Tailor SYSML
« on: February 13, 2020, 09:40:27 pm »
I recomment to contact Sparx.

Pages: 1 [2] 3 4 ... 58