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 - Eve

Pages: [1] 2 3 ... 483
It's only if you have more than one parameter the you get a syntax error.
Presumably because it ends up being a parenthesized expression instead of parenthesis around the arguments.

Easy question first.
1 It actually generates a slightly (but not substantively) different specification!  :o  The baseStereotypes are always in ascending alphabetical order and the generalizes attribute is always the first alpha stereotype!  ::) (who dreamt that one up?)
Connectors (unfortunately) are not an ordered relationship. I don't know why EA needs both generalizes and baseStereotypes. What I do know is that prior to it being being explicitly alphabetically ordered the order was unstable. It created a lot of extra work when generating a large technology and reviewing the changes. (Also for tagged value connectors and the three metamodel constraints.

I hope you can agree that any defined order is better than no defined order.

In terms of your actual issue...

Am I correct in my understanding that stereotypes extending EA relationship types aren't inheriting their constraints? Is it just with multiple inheritance or does it fail for all inherited constraints?

I can't point you to a specification of what the "correct" format is. That's because the assumption has always been that it will be consuming what EA has generated. We specify how to create it in your model, not what the file needs to look like. Nothing has changed in that area. If you choose to create a file yourself, it is your responsibility to emulate what EA would have generated.

Given bad input the behavior is undefined1. As long as Enterprise Architect hasn't crashed or hung on that input I don't see why development and testing effort should be redirected2 away from where they are allocated.

1 a word that has been used in computing to describe the result of invalid inputs from the start.
2 those things are a finite resource. Looking at this would come at a cost to another area.

Yes, Enterprise Architect will only generate the latter form and will not accept the former.

There is no "should". If you are hand modifying something it is your responsibility to put it in the correct format.

So instead of MyProfile::MyToolbox, the string MyToolbox is sufficient. That's a bit confusing since you cannot refer to the UML Component toolbox with Component but have to use UML::Component.
Within your technology you are already in your namespace. UML isn't the default namespace.

General Board / Re: Import XPS or Visio into Sparx
« on: July 31, 2020, 12:17:49 pm »
I know that bit isn't easy... Still had to be said.

General Board / Re: Import XPS or Visio into Sparx
« on: July 31, 2020, 08:31:32 am »
Find a converter to convert xps to emf and import those.

You could also get people to export to emf instead.

If you're really luck you could convince them to use EA instead of Visio.  ;)

There's no direct query for getting a toolbox name. In most circumstances you are referring to a toolbox you are creating.

Both parts of the name you have used there are the "friendly" names. The actual id is SysML1.4::InternalBlock.

PS. The linked help includes the following hint to find the id to use for non-uml diagrams.

Note: If you do not know the fully qualified name of the diagram type you are extending, query the API to get the 'Metatype' field. In a Javascript console you can use:

What form is your toolbox specifying the item?

It should work if you fully specify it. ie. MyProfile::Grouping(UML::Component). If you only specify the stereotype but not the applies it doesn't know which extension to use.

When you extend Class on the specialized type instead, it still only extends class and the settings within that extension override the base one.

I would always create an abstract stereotype without an extension when I plan to specialize it from stereotypes that extend different metatypes.

No, support for that driver was added after 13. You won't find it mentioned in the user guide for your version.

Following selecting and dropping actions do not propose this "Realization" link - choice is limited to Dependency, Trace or Information Flow.
Realization isn't offered by the current toolbox, which means that it isn't offered by the quicklinker by default.

You will find the option to turn off the filter to toolbox in the quicklinker menu.

There currently isn't a separate import, but importing the Jscript library will have the same effect.

You state that you are using 14 with the issue. Now you say it works with 14?
What I see is that the same version of EA fails after updating SQL Server.

I'm currently connected to a SQL Server 2016 repository, from what I've seen there are no documented compatibility issues going from there to 2017.

General Board / Re: back button
« on: July 14, 2020, 02:15:02 pm »
Ctrl-Tab works usually to get to the previous diagram, but you can't use it to get to the one before that (to go back - back) because it then toggles between the two last diagrams.
If you hold ctrl you can press tab multiple times to go further back in the history. You can also click on an item in the list.

Pages: [1] 2 3 ... 483