Hello jthyge1

I would say this solution is too static.

You can read out the name of a Screen in a Script for example with GetPictureName (C) if you use Picturewindows. or you just read out the picturename property of the picture window.

You can also use the Openpicture event of a screen to use a small vb script and write the Objectname of the screen to a internal string tag (what you can display)

The possibilities in WInCC are so big that you can achieve this usecase with a lot of ways but a static textlist would be a non-smart solution...

If you want to do so then I would use a internal tag for the index that is "computer-local". THis has its own context on any client or Runtime instance.

(I hope you are talking about WInCC V7/8?)

Bye Murof

Hello jthyge1

Every client (Web client/WebUX or HW Client) has its own istance. every Instance has its own runtime. And if you use  internal Tags that are sessionlocal in the settings then they have its own value on every client instance.

So you can of course work with help tags for the text information then you would not have to use scripts or similar.

In VB Script its very easy to go to the parent screen context. Here you can use the parent operator

-> look in the WinCC help for parent

Bye Murof