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 - Simon M

Pages: [1] 2 3 ... 434
That's a strange use of the term "Active".  I thought unmarking the MDG list stopped the toolboxes from appearing.  Since you can ONLY set ONE of any enabled MDGs to be active I would have thought, by definition,  "All enabled MDGs are created equal, but the active MDG is more equal than others".
I may have misunderstood you.

The 'Enabled' checkbox for each add-in is the GUI state. ie. (It can be shown by a perspective)

The 'Active' flag that can be set for a single technology does give it special priority, but only in a limited sense.
Setting a Technology to Active makes that Technology your default interface to Enterprise Architect, and can:
  • Override various Toolbox pages (including those from other Technologies) with pages specific to the active Technology
  • Redefine a stereotype in another profile, adding new tags and removing or modifying existing tags, while the stereotype behaves in all other ways as if it is the original stereotype
If your preferred Technology does not use overrides and redefinitions, it is not necessary to set it to Active.

Given you would have to have other technologies enabled for either of those, I can safely say that enabling your technology will have no impact on your situation. There's no "post truth" or anything going on.

So I tried to do what is suggested in VBScript
Code: [Select]
foundConnector.Stereotype = stereotype
 foundConnector.StereotypeEx = "MDG::" & stereotype
Setting the breakpoint at the second statement, foundConnector.Stereotype is set to the value of the Stereotype ("Cmpstn").
After the StereotypeEx assignment, both foundConnector.Stereotype and foundConnector.StereotypeEx are set to empty string!  I'm assuming that's NOT supposed to happen.  So what, if anything am I doing wrong?

For a start, never assign to Stereotype. Seriously, never so much as look at it.

The fact that you're getting an empty string is probably a good thing. It means that you're trying to use a fully qualified name that doesn't exist, or can't be applied to that type. Setting the Stereotype after StereotypeEx is bypassing that, and again telling EA to guess where the stereotype comes from.

Are you using the technology name or id instead of the profile name? Does the connector type actually match the type the stereotype is extending?

EA only assigning your stereotype if a matching stereotype exists in the stereotype table could be an indicator that it's actually matching your stereotype despite it not matching the base type. I can't tell without knowing what connector type you are creating, what the stereotype in t_stereotypes is extending and what your profile stereotype is actually extending.

Based on you setting Subtype I'd say that you are trying to extend "Composition", which doesn't have a corresponding metatype, but that's a guess. It's also worth knowing if you can reproduce the behavior with a profile created by EA instead of your own, which may have something that is confusing EA.

Did you know that you could pass a qualified metaclass name (<profile>::<metaclass>) to Connectors.AddNew? Would mean you don't need to explicitly deal with the stereotype at all.

NO, I specifically excluded ALL but my active MDG
You prevented them from showing in the toolbox etc. That's all that option does. The other technologies are explicitly still available to ensure existing models using them still appear correct.

By definition, it should look in my (Active) MDG FIRST then if not found, look elsewhere!  What so hard about that concept?
The concept is easy. The problem is that your definition doesn't match the actual definition of that option.

Does this process ENSURE you DON'T get a general stereotype anomalously created?   That is, it will NOT (in your experience) create "MyProfile::Goal" (as we have seen).
From 1425, EA blocks creation of new stereotypes containing "::". You shouldn't see them created. The other thing I would suggest is disable the Configure Stereotypes for all users. This will prevent extra stereotypes being defined from typos etc.

As Geert said, always use the fully qualified name. If you don't, EA will try to guess your meaning. And it will probably get it wrong.

Automation Interface, Add-Ins and Tools / Re: EPPRofile:: ?
« on: December 12, 2018, 10:01:03 am »
The id of the technology is EP. EPProfile comes from the profile name.

PS: Nevertheless, it IS a bug isn't it?
Why? You've asked EA to find a Goal stereotype and assign that to the element. That's exactly what it has done.

It's explained here:

Additional Permissions for Project Transfers
When an Enterprise Architect repository is transferred into a SQL Server based repository, it is necessary for Enterprise Architect to execute a number of SET IDENTITY_INSERT (table) {ON | OFF} commands during the process. This means the user performing the transfer must have a high level of security, in the role of 'db_ddladmin'.

General Board / Re: Are spammers the main users of this forum?
« on: December 10, 2018, 12:42:09 pm »
There is a filter...
A filter that not filters is not a filter.
Comparing logs for where filters have been applied vs where new ones have been added I estimate it's catching around a third. That doesn't account for any that fail a captcha etc.

So it's preventing a significant amount, but I share your frustration at the amount that isn't being prevented.

Automation Interface, Add-Ins and Tools / Re: Reverse engineer MDG
« on: December 10, 2018, 11:21:23 am »
There's nothing from Sparx Systems to do this. (Released or internal)

Then you'll still require multiple passes through the list won't you? Check each object against all possible parents/children. You can optimize by starting after the element you're checking, but I can't see that you'll only need a single pass.

I'd say that the order is a product of the internal ordering rather than something official.

That said, I can't see a reason why it would be changed.

PS. Looking for a single object enclosing "the rest" of the selection?

General Board / Re: Multiple use of elements in diagram
« on: November 29, 2018, 10:56:19 am »
Why should I not be able to place two workstation Wintel devices and Web Browser execution environment in each?? Plus a bunch of Tab execution environments in each of these execution environments. Sparx again failed to grasp the essence of UML
Sounds like what you are wanting is to place two instances, not the classifier.

The advice that same element multiple times introduces ambiguity is about the classifier, and the confusion you're demonstrating makes me glad that EA doesn't allow it.

PS. The comment that you are quoting isn't from a Sparx representative.

When I am exporting the diagram as a profile I can import it and it works.
However, it does not overload the profile that I have used so far, because it generates a different value for the Documentation/@id attribute.
Then it's probably an export of that package that you have previously used.

What changed is that you have a single ribbon menu item that will select either the diagram or package to export. Whichever one is being exported isn't the same as the way you were doing it in 13.5.

Select the package in the project browser immediately before running the export.
If that doesn't work, click in the diagram immediately before running the export.

Start by removing the language macro for nullptr.

My guess is that it's failing because of the noexcept on your functions.

If I'm right, you should be able to get further by adding language macros noexcept and noexcept().

If you want to contact support, I expect we should be able to provide an MDG technology that adds that as a tagged value instead of skipping over it, as well as adding the support to a future version.

Uml Process / Re: Signals - "Details" tab not displayed
« on: November 20, 2018, 12:24:12 pm »
The details page exists to provide other options that aren't available for other types. It's only an artifact of history that it provides access to the Attributes and Operations. It's never been the primary way to access those windows.

Uml Process / Re: Signals - "Details" tab not displayed
« on: November 20, 2018, 09:33:49 am »
I need access to Attributes and Operations...
Design > Element > Features > Attributes
Design > Element > Features > Operations

Alternately, F9 and F10.

Pages: [1] 2 3 ... 434