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
84612members
353911posts

[Imported] Mimic layer visibility, multiple registry expressions on a single button

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
734

[Imported] Mimic layer visibility, multiple registry expressions on a single button

>>Message imported from previous forum - Category:Scripts and Tips<<
User: hardin4019, originally posted: 2019-07-22 16:28:41 Id:476
I have working mimic layer with visibility buttons ( 1 for RTU Health, and 1 for Location info) that each toggle the visibility of their own layers. The annoying thing I am trying to work around, is that the layers are stacked, and if you turn on the top layer, you can't see the bottom layer without first turning back off the top layer. Is it possible to have both buttons not only turn on or off (iif Statement) their respective layer, but also turn off the visibility of the other layer with Registry expressions? Or are there better options for completing the task?

RTU Health button PickType 8, PickParam:

'ShowRTUHealth( ' + IIF( Registry('ShowRTUHealth', 1 ) = 0, '1', '0' ) + ' ) '

RTU Health Layer Visibility Expression:

Registry ('ShowRTUHealth', 0) = 1

 

Location Button PickType 9, PickParam:

'ShowLocation( ' + IIF( Registry('ShowLocation', 1 ) = 0, '1', '0' ) + ' ) '

Location Layer Visibility Expression:

Registry ('ShowLocation', 0) = 1


Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
733

Re: [Imported] Mimic layer visibility, multiple registry expressions on a single button

>>Responses imported from previous forum


Reply From User: sbeadle, posted: 2019-07-23 13:42:18
You can use script to cause multiple registry changes (there are registry functions available within the script code).


Reply From User: hardin4019, posted: 2019-07-31 19:31:20
Thanks sbeadle, that works like a champ.


Reply From User: geoffpatton, posted: 2019-08-01 13:59:03
Why even use the registry? I just use vb script to change the visible property on mimic layers.


Reply From User: hardin4019, posted: 2019-08-01 14:09:28
Not sure that there isn't a better way of doing it... But for what I am doing, it works great. To be clear, I'm turning on the visibility of a single layer with the button and turning off the visibility of other layers if they are already on, but for multiple templated mimics, that are embedded into a single screen. Also it is nice that the registry is independent on each workstation since I have multiple work stations per system and do not want the layer visibility changing on the other work stations.


Reply From User: geoffpatton, posted: 2019-08-02 17:30:17
I use it on both layers and objects. Using the script is independent on each station, it does not change anything in the saved version of the mimic.

Actually when I tried using the registry it changed all the clients or maybe it was all web clients. I figured I might be doing something wrong, or it is because the WebX uses the server's registry. At the same time I figured out the Scripting and have not looked back at the registry. I prefer keeping things inside the software if I can also. I have had enough new IT rules mess with customers systems to be skeptical. I think that anything I do outside of the software increases the odds that IT will break something.
I have also used the state of variables to control visibility.

I love flexible software

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
734

Re: [Imported] Mimic layer visibility, multiple registry expressions on a single button

>>Responses imported from previous forum


Reply From User: sbeadle, posted: 2019-07-23 13:42:18
You can use script to cause multiple registry changes (there are registry functions available within the script code).


Reply From User: hardin4019, posted: 2019-07-31 19:31:20
Thanks sbeadle, that works like a champ.


Reply From User: geoffpatton, posted: 2019-08-01 13:59:03
Why even use the registry? I just use vb script to change the visible property on mimic layers.


Reply From User: hardin4019, posted: 2019-08-01 14:09:28
Not sure that there isn't a better way of doing it... But for what I am doing, it works great. To be clear, I'm turning on the visibility of a single layer with the button and turning off the visibility of other layers if they are already on, but for multiple templated mimics, that are embedded into a single screen. Also it is nice that the registry is independent on each workstation since I have multiple work stations per system and do not want the layer visibility changing on the other work stations.


Reply From User: geoffpatton, posted: 2019-08-02 17:30:17
I use it on both layers and objects. Using the script is independent on each station, it does not change anything in the saved version of the mimic.

Actually when I tried using the registry it changed all the clients or maybe it was all web clients. I figured I might be doing something wrong, or it is because the WebX uses the server's registry. At the same time I figured out the Scripting and have not looked back at the registry. I prefer keeping things inside the software if I can also. I have had enough new IT rules mess with customers systems to be skeptical. I think that anything I do outside of the software increases the odds that IT will break something.
I have also used the state of variables to control visibility.

I love flexible software