-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conditional connectors not handled by OMEdit #2081
Comments
See original ticket description on trac #2081. |
@adrpo, I'm trying to figure out myself why this is so difficult. I tried a simple example case, see As I understand the problem is that currently OMEdit fetches display information from the class definitions
but not from the actual instances. Specifically, it gets the information that TestConditionalConnectors.Test1 contains an instance of class TestConditionalConnectors.M1 named m1, but then it asks about elements of the class M1, not of the specific instance m1, which is were the information about the activation of conditional connectors is defined. Do I understand correctly? Is the problem that we should switch from gathering information about classes to gathering information about their instances? |
The current situation is that all conditional connectors are always shown. There were some cases where this did not happen, see #8172 and #8210, they were fixed in #8237. Other cases are more involved, e.g. because of redeclared classes, see #8210, and cannot be easily fixed with the curent approach. Eventually, once the new instantiation-based framework is established, #8237 should be reverted and the visibility attribute should be correctly evaluated in OMEdit based on the latest parameter value input. |
Additionally, we need to update the icons that depend on parameters dynamically. |
Prototype implementation available since PR #9230, start OMEdit with MWE: TestConditionalConnectors.mo.txt, R1 has an activated thermal port, R2 hasn't. Changing the parameter useHeatPort of R2 immediately affects the status of the conditional connector shown on the diagram. |
@adeas31 I tried the prototype with our BRSL pumps library and for the pumps components. I now only see a blank diagram or OMedit crashes. Also the error appears: |
@niklwors, thanks for reporting! What we have now is just a demo. It shows we are on the right track, but is still far from being usable. Work on that will resume from mid-August. |
@niklwors please send your library to me. I will do some testing. |
@niklwors several improvements are done. Can you please test this again and report. |
This functionality is now implemented for good in the new instance-based API, currently activated by running Please reopen this ticket if there are any problems which are specific of this feature. |
No description provided.
The text was updated successfully, but these errors were encountered: