Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84248members
353348posts

[Imported] Any way to change inset window dimensions based on something in the mimic in the same inset window?

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Solved
sbeadle
Janeway Janeway
Janeway
0 Likes
1
484

[Imported] Any way to change inset window dimensions based on something in the mimic in the same inset window?

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: hardin4019, originally posted: 2019-03-19 16:59:36 Id:384
I have a valve face plate with a trend displayed on the right side. My users have asked if it is possible to make it so that they can minimize the trend and only see the points in the mimic to the left of the trend, as the trend is not always necessary and sometimes blocks things in the background that they need more than the trend. Is there a way to resize an inset window with an animation triggered by a button in the mimic?


Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
483

Re: [Imported] Any way to change inset window dimensions based on something in the mimic in the same inset window?

>>Responses imported from previous forum


Reply From User: dmercer, posted: 2019-03-19 21:15:48
The question at the end doesn't quite gel with the problem description for me.
If the trend is embedded on the faceplate and you want to hide the trend, then you can use the Visible animation parameter on the embedded trend. I don't think that you can resize an already open inset window from a script though.


Reply From User: geoffpatton, posted: 2019-03-19 22:46:30
Even if you could resize the window, the contents of the screen would resize to fit the new window size.
When you say in the background are you meaning the Parent window?
In that case hiding the trend object by its visible parameter wouldn't be helpful, but if you have two mimics for your inset you can use buttons with the hyperlink pick action set to Navigate and Resize to switch between them.


Reply From User: hardin4019, posted: 2019-03-19 23:11:55
Sorry, the background I'm talking about is the parent window, and not the same inset window. Resizing the inset window to a narrower size without shrinking the contents is the end goal. The trend is imbedded in the right side of the mimic (both mimic and trend are in the inset window).

Option B, I could put the trend on a different layer and leave a button for the operators to make it visible only when they need it.

Option C, I could leave the trend out and put a hyperlink in to open it in a second inset window.


Reply From User: hardin4019, posted: 2019-03-21 15:22:52
Questions regarding the execution of Option B. I took my templated valve face plate and added a button that changes a "ShowRTUHealth" registry to hide a layer containing RTU Health related points. The only issue I have doing this is that if I have multiple valve face plates embedded in a mimic, clicking the button on a single face plate causes the RTU Health points to be displayed on all of the valve face plates. Is there a way to make it independent per embedded face plate using the registry, or am I better off adding a point or entry in the mimic or group that that indicates whether the RTU Health data is visible?


Reply From User: dmercer, posted: 2019-03-21 21:12:39
Normally I would store the visibility setting in the registry. If you use the registry to hold the visibility setting, then include the FullName of the device in the registry string, that way each one will be unique.

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
484

Re: [Imported] Any way to change inset window dimensions based on something in the mimic in the same inset window?

>>Responses imported from previous forum


Reply From User: dmercer, posted: 2019-03-19 21:15:48
The question at the end doesn't quite gel with the problem description for me.
If the trend is embedded on the faceplate and you want to hide the trend, then you can use the Visible animation parameter on the embedded trend. I don't think that you can resize an already open inset window from a script though.


Reply From User: geoffpatton, posted: 2019-03-19 22:46:30
Even if you could resize the window, the contents of the screen would resize to fit the new window size.
When you say in the background are you meaning the Parent window?
In that case hiding the trend object by its visible parameter wouldn't be helpful, but if you have two mimics for your inset you can use buttons with the hyperlink pick action set to Navigate and Resize to switch between them.


Reply From User: hardin4019, posted: 2019-03-19 23:11:55
Sorry, the background I'm talking about is the parent window, and not the same inset window. Resizing the inset window to a narrower size without shrinking the contents is the end goal. The trend is imbedded in the right side of the mimic (both mimic and trend are in the inset window).

Option B, I could put the trend on a different layer and leave a button for the operators to make it visible only when they need it.

Option C, I could leave the trend out and put a hyperlink in to open it in a second inset window.


Reply From User: hardin4019, posted: 2019-03-21 15:22:52
Questions regarding the execution of Option B. I took my templated valve face plate and added a button that changes a "ShowRTUHealth" registry to hide a layer containing RTU Health related points. The only issue I have doing this is that if I have multiple valve face plates embedded in a mimic, clicking the button on a single face plate causes the RTU Health points to be displayed on all of the valve face plates. Is there a way to make it independent per embedded face plate using the registry, or am I better off adding a point or entry in the mimic or group that that indicates whether the RTU Health data is visible?


Reply From User: dmercer, posted: 2019-03-21 21:12:39
Normally I would store the visibility setting in the registry. If you use the registry to hold the visibility setting, then include the FullName of the device in the registry string, that way each one will be unique.