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 ... 55
I realized that now, when you drag and drop an element from one diagram to another, the element is relocated under the assumptions that the element should have the same place as if it was created on the diagram.
However, if you want to show the element on several diagrams by creating the drag and drop link, this new (at least for me bad feature) causes the element to jump around within the repository each time you put it to an additional diagram.

Bugs and Issues / Re: Build 1512 seem to have serious bugs
« on: September 30, 2019, 09:00:46 pm »
Here is some additional feedback.
2) I have not seen that any more so far. However I am quite sure that it was not a scrolling thing, because I missed the head and not the tail.

1) I see very frequently. It is not really related to signal assignment to triggers. It is about the “Unsaved Property Changes” dialog which appears most times (but not always!?) when you changed a property after you select something else. When you do some of this property changes it takes not to long time and neither “Yes” not “No” nor “X” closes that dialog. After pressing several time on those controls, the dialog is closed,  but EA does not carry out any command after that.
A bug report I will send today.

Bugs and Issues / Build 1512 seem to have serious bugs
« on: September 26, 2019, 01:26:48 am »
Just working 5 minutes with build 1512 I had two strange issues.

1)   After assigned a signal to my second trigger a signal, I got the message box that the trigger has changes. However both OK and Cancel opend the message box again. After clicking around several times the message box was gone closed but EA as well (just frozen). With my first trigger I did not have that problem?!
2)   One of my diagram tabs do not show the name of the diagram but only the last two letters of the name.

Just finding those things in this shore time let me fear that the 1512 buld might have much more surprises or;
 I am the world best tester. ;)

General Board / Re: Can I exclude ports from report generation?
« on: September 06, 2019, 11:24:31 pm »
Assuming that you are talking about elements and not diagrams, you should be able do that with template selectors e.g. by caling a template for ports doing nothing.

In general this example diagram looks a bit strange to me, because the IDB seem to have blocks rather than parts.

Ignoring that fact, SysML allow connecting parts without ports. Not using ports to connect part1 with part 2 means part1 is connected somehow to part2 but I do not tell you how or I do not know how.

If the two parts are connect with ports having classifiers, it means part1 is connected with part1 port and the details are defined in the part1 port classifier to part2 with the part2 port and the details are defined in the part2 port classifier.

If they had added the counterpart ports to the CAN_Bus as well, it would make clear that there is a one to one relationship between ports.

Without those ports, you are allowed to implement that one to one relationship, or you are allowed to implement a one to one relationship ports within a super port, or you are allowed to implement a super port which can handle all ports connected to CAN_Bus in common.

In other words, yes there is a semantical difference.

General Board / Re: Naming conventions for interfaces between SysML blocks
« on: September 05, 2019, 03:04:04 am »
In such a scenario, I typically give no port a name, but only a classifier only.
The drawback in EA is, that within some EA feature, the names are relevant to distinguish because; classifiers are not shown in those features.

However, by doing so, you get just rid of your problem of thing about the port names. I use port names manly to distinguish, when I have several ports with the same classifier.
If you use the interface block for both sides you have to set the isConjugated (as you have done), because in fact an interface has a provider and a consumer somehow. In this sense the interface block is a kind of short cut.

Your port names are for sure legal, but at the end, those names define somehow what ports of the OS should be connected which ports of the middleware. Once the connection is established in the IBD it is just done.

In principle you could do reverse engineering to get modelling elements representing you code. This, I assume works fine for OO languages (I did already for Java). If reverse engineering of c-code would work as well, you need to find out somehow.

Hi Fabio,
Here you might get some feedback or you might get not. To rise a real bug report you should go to Sparx homepage under „Support/Contact Us“.

Hi Fabio,
page 148 is just graphics and do not tell so much.

But when looking on page 151
“An Action appearing in an “AllocateActivityPartition” will be the /client (from) end of an “allocate” dependency. The element that represents the “AllocateActivityPartition” will be the /supplier (to) end of the same “allocate” dependency. In the «AllocateActivityPartition» name field, Properties are designated by the use of a fully qualified name (including colon, e.g., “part_name:Block_Name”), and Classifiers are designated by a simple name (no colons, e.g., “Block_Name”).”

I think you are right, but it seems to be ignored by EA. Maybe you issue a bug or a feature request.

if you want to use the relationship matrix you need to establish a real relation by an sysml <<allocate>> relationship.
What you are doing here, is not much more than a visualization of relations you do not have in your model.
Of cause it would be nice if EA would establish that relation for you in background, but it does not and the omg standards are very inconsistent in how to handle “containment”.

Automation Interface, Add-Ins and Tools / Re: report templates
« on: July 15, 2019, 10:39:44 pm »
I am only 99.99% sure, because sometimes I find some tricks to make impossible things possible.
However I remember that I tried it again, but gave it up. What is missed, is that you can not use the template selector for packages as well.

Oh, yes! This is what I was looking for. Thank you KP!

In V15 when you double-click on a diagram element, e.g. to open a composite diagram, the current diagram is closed. By an arrow you can move back to the original diagram.
In former version all diagrams are kept open.
If you navigate/hop to different parts of the "diagram hierarchy", before V15 you might end up with lots of diagrams opened, what is not so nice. Now only one diagram is open, what is nice if you used this hopping just to get to that diagram.

However I use this hopping most frequently to open at least two diagrams. One diagram I want to change and the others to look what I have to do. This more frequent use case (at least more frequent use case for me) worked fine for any version before V15.
To address both use cases, I would prefer a simple way to decide if I want to keep the current diagram open or not before I hop to the next.
If this is not possible for whatever reason, I would very much like if the V15 change would be cancelled.

What is the opinion of other users?

I assume stirring the menus each time around, is not intended to be an improvement of EA, but to be a improvement of us, by finding features you have never missed when searching the features you need.  ;)

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