A submodel is shown in a model diagram while its pathname is wrong and the model doesn't simulate

[massimo ceraolo]

Consider the model InvPwmPQ in the attached package invPwmPkg.
I'm not sure whether its sub-model PwmPulser has a valid pathname.
But whatever the answer OMEdit seems inconsistent:
1) its icon is visible in the InvPwmPQ diagram
2) when the model is checked the following error is issued:

Error
[invPWMPkg: 12:5-12:156]: Class invPWMPkg.PwmPulser not found in scope invPWMPkg.InvPwmPQ.

I think that if PwmPulser is not in scope, its icon should not be visible.

* A later addition: comment 3 explains that PwmPulser is not in scope, and therefore it should not be visible in InvPwmPQ.

[Per Östlund]

The model is invalid, because looking up invPWMPkg requires going to the scope outside invPWMPkg. But since invPWMPkg is encapsulated that's not allowed. So to fix the model, just remove the invPWMPkg prefix from the pwmPulser component.

The icon lookup doesn't seem to follow those rules though, so that should be fixed.

[massimo ceraolo]

Ah. I did see that removing invPWMPkg prefix made the model solvable, but failed to track down this to the encapsulated keyword.
Naturally, the core of this ticket was consistency in OM behaviour (so perost's last sentence).

I must add that I'me pretty sure that somehow invPWMPkg prefix was created by OMEdit itself. If confirmed, that is another issue. I will try to produce an example to reproduce this.

[Francesco Casella]

Rescheduled to 1.14.0 after 1.13.0 releasee

[Francesco Casella]

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0