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 ... 539
1
As for why I'd want to do this: I, long ago along with a lot of the software world, moved away from putting the "type of the thing in the name of the thing" when it can otherwise be inferred from context - e.g. in code, I don't say
Code: [Select]
int intValue = 1;but instead
Code: [Select]
int value = 1;and it's the same here - it just feels clumsy.

I traced this back to the SysML 1.5 (and 1.7) specification but it doesn't say anything on the matter. It gives an example of applying the same stereotype to different metaclasses and applying the same properties (which is what EA does), but doesn't seem to explicitly include or exclude using the same-named stereotype on different metaclasses.
If it helps, the profile is a Namespace. Two stereotypes with the same name are not distinguishable from each other. (Look for isDistinguishableFrom in the UML specification, which is not overridden by the Stereotype class)

To compare it to your code example, if you needed an int value and a float value in the same namespace/scope you would need to rename one or both.

2
We recommend removing the relevant files from the EA installation folder, located at: C:\Program Files\Sparx Systems\EA\MDGTechnologies
That advice is so bad I'm going to track down who gave that advice and ask them to send you a retraction and apology.

As described by Geert, perspective sets are the way to do this. It allows you to limit the technologies available to all users of that model or limit specific user groups in your model.

3
I'm not sure if the developers of LemonTree are active on this forum. I'd recommend directly sending them a support request.

4
Could you tell me please why VCEs are the correct way to manage multiple copies of elements on a diagram? How tells us that only an element can be represented only once on a diagram?
Paolo's reasons are probably different from mine, but we looked at the kinds of diagrams users were saying they couldn't create because of the limitation of showing each element only once. The common story was that a complex layout meant they needed a way to show one end of a connector closer to the other end. That's what was implemented.

Issues are in fact: no possibility to resize, and not possibility to not use rectangle notation.
Neither of those are reasons why the virtual connector end is an inappropriate solution. I would describe them as a request for more options for the existing feature.

5
That works for templates, so I guess it will work for searches as well.
No. Searches just use the column 'Note'. The trick is that the default behavior is not to show the Note for each item. Click on the dropdown button second from the right in the toolbar. There's an option 'View Notes' that provides 3 levels of display.

6
You’ll likely need to define the ISO 80000-based units yourself as a reusable package or profile. EA provides the modeling tools to do so, but does not include the data pre-installed.
Ignore this.

In the 'Create from Pattern' tab in the Start Page, you can find the 'ISO 80000 Library (Downloaded)' pattern in the SysML 1.5 Library group.
This is the answer.

7
Quote
FQStereotype        The fully-qualified stereotype name in the format "Profile::Stereotype". One or more fully-qualified stereotype names can be assigned to StereotypeEx.
Then I'm happy to be proven wrong and there has been further development in this area that I haven't remembered.

If it's working when you have that permission then it sounds like it may be a bug.

8
StereotypeEx doesn't support assigning multiple stereotypes. Because it doesn't find a single stereotype matching what your code specifies it's trying to define a new stereotype. You don't have permission to do that in your model.

9
Can I suggest Repository.CurrentSelection, which gives you more information about what is selected.

EASelection Class

It will tell you that the selection is on the diagram (selection.Location == "Diagram"), the element being displayed in all the properties windows, (selection.Context) and the full list of the elements in that selection. (selection.List)

Those are all properties that are available without additional database queries. You can use them in locations like building menus or update commands without negatively impacting performance. The final significant property for that object is the ElementSet, which will load all of the selected objects. It will be a faster way of accessing all of the selected objects than calling Repository.GetElementByID or Repository.GetElementByGuid for each item individually.

10
General Board / Re: SQL object update
« on: April 04, 2025, 11:27:28 am »
If you're talking about Repository.SQLQuery or any place in the UI that allows execution of SQL, EA will not run that statement. We strongly discourage / don't support any modification of the model via direct SQL.

11
That's explicitly something that we won't add to the API because the end user needs to make that decision, not some random add-in author.

12
General Board / Re: How to export a diagram to draw.io?
« on: March 14, 2025, 10:17:38 am »
The general answer is that you look at the export and import formats supported by any two tools to find an intersecting format.

The most likely standard formats that Enterprise Architect supports that another BPMN 2.0 tool may support are BPMN 2.0 XML and XPDL 2.2. I don't know if draw.io supports any exchange format, or even creating a model instead of a diagram.

13
I'm sorry, I'm a little confused.

reverse engineering it with Eclipse

After refreshing the project and synchronizing the deleted class in the code, I expect it to be deleted from the diagram and project browser, but sparx does not do this automatically. I have to delete it manually.
Those two statements seem completely unconnected.

14
General Board / Re: Value Type, Quantity Kind and Units
« on: February 06, 2025, 11:55:02 am »
I randomly stumbled on his thread and wanted to try the ISO 80000 Library.
But I get an error message, when selecting it in the Model Builder.
Pro tip. It helps you to get useful replies when you provide the error message instead of just saying you got one.

15
but exponentially faster in EA compared to the others
Linearly. If you increase change the value it will change the same proportion of the original value in both EA and other applications that are doing the right thing.

As Georgi says, it looks like the problem is just that the line height being used is higher than you're expecting (and I can understand why). I am almost certain that there is no option for EA to change that line height.

Pages: [1] 2 3 ... 539