nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Diagnose mediniIdentifier

medini_1052680584

Dear ANSYS team,

Sometimes the mediniIdentifier shown by using the option "diagnose->what is this?" on a marked element in model browser is different from the mediniIdentifier I get with a simple script like:

selection[0].mediniIdentifier;

Why is that and how do I get the mediniIdentifier shown by "diagnose->what is this" (since this last one seems to be the one used by medini's diff when comparing two files)?

Thanks for a feedback!

Cheers, Andre

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1059007410

Hi Andre,

That's quite well explained in Jan's article: https://medini.freshdesk.com/a/forums/topics/1000106116

Checking for the existence of a proxy is done at the "isEmpty()" function, you could use that if you want to find out. But in principle proxies are used to link something into the project tree of packages. Best to see via the Attributes (what is this?) view.

Happy Scripting,

Nils

All comments

medini_1059007410

Hi Andre,

I would expect the mediniIdentifier for the same object always to be the same from script or Attributes view ("what is this?").

One situation I can think of where you get differences between Attributes view and script is a (FTA/Requirements etc.) model. There the Attributes view initially shows you the proxy, until you go via "originalModel" or the button "Resolve" to the actual model. "selection[0]" directly resolves the proxy to the actual model, I think.

Is that the cause for the difference you've seen, or in which situation does it appear? Do you have an example?

Happy Scripting,

Nils

medini_1052680584

Hi Nils,

That would also be my expectation and it is usually like that, but there are exceptions apparently.

In the example below I just created:

- a package

- a new system model

- an element in the system model

(marked in green)

I compared the mediniIdentifier of the "what is this?" with the output of

console.log(selection[0].mediniIdentifier);

It matches for all except for the system model (marked in blue).

The mediniIdentifier which the script shows is the one one gets if I double click on

the originalModel (marked yellow).

I am experimenting with changing mediniIdentifiers in order to control better the diff comparison.

Cheers, Andre

medini_1059007410

Hi Andre,

Yes, that's what I meant. There is no issue with the mediniIdentifier, it's just about what kind of object you are looking at. A system model is linked via a proxy into the medini project, and the proxy is an own object and thus has its own mediniIdentifier. The "selection" doesn't give you that proxy, but already the system model (because it was "resolved", as for example also M2Doc does it).

If you console.log("{0}", selection[0]); you will see the actual object printed, including its type (e.g. SysMLContainerPackageImpl). That makes it probably clearer to understand what you are looking at.

Does that answer the question?

Cheers,

Nils

medini_1052680584

Hi Nils,

Thanks for the clarification concerning proxies.

While scripting: from the system model, how can I find its proxy?

How can I find out if a selected element has a proxy?

Cheers, Andre

medini_1059007410

Hi Andre,

That's quite well explained in Jan's article: https://medini.freshdesk.com/a/forums/topics/1000106116

Happy Scripting,

Nils

medini_1024169437

Oy my dear, every second word has a typo inside in that article, tons of "modle" instead of "model", seems like I was in a hurry :-)

Jan