Commands to manipulate InTouch from windows

From what I can recall, it is possible to pass the application path as argument to view.exe but I'm not sure if it supports any more parameters than that. For instance, view.exe "C:\Apps\MyHmiApp" will attempt to open an InTouch app at that location.

The official parameter that I have found is indeed the application path.
But there has been some information that there are switches to use as a command available.

view.exe /ReadOnly should for example open the application in read only mode, (in some newer versions and in OMI).

I would believe that any additional information on how to use parameters or switches has to come from un-documented suggestions from developers or techsupport.

But going back to the original question of controlling windows externally is in some way a security risk.

At least without any active control from the application it self.
If this was a possibility, then I could, by using the ww_wdws.ndx file, review all available windows in the application and the open them one by one by using this switch.

ie. view.exe /w AdminWindow

Thus by-passing all built in navigation related security in the application.

In the cases where I have seen external references controlling witch window to open, then it has to be a conscious decision from the developer. 

For example having InTouch reading from a config file when starting, opening windows based on the content there, or script checking node name deciding what window to open.

For external triggers, have a Suitelink/OPC (or legacy DDE) client that triggers tags in InTouch that by scripting opens the desired window.

But history has shown me that there are indeed a lot of tricks that are usually on a need-to-know basis, so I can imagine someone else has some experience that is closer to what Olav is asking for.
Or any other view.exe /switch trick that is available.

The official parameter that I have found is indeed the application path.
But there has been some information that there are switches to use as a command available.

view.exe /ReadOnly should for example open the application in read only mode, (in some newer versions and in OMI).

I would believe that any additional information on how to use parameters or switches has to come from un-documented suggestions from developers or techsupport.

But going back to the original question of controlling windows externally is in some way a security risk.

At least without any active control from the application it self.
If this was a possibility, then I could, by using the ww_wdws.ndx file, review all available windows in the application and the open them one by one by using this switch.

ie. view.exe /w AdminWindow

Thus by-passing all built in navigation related security in the application.

In the cases where I have seen external references controlling witch window to open, then it has to be a conscious decision from the developer. 

For example having InTouch reading from a config file when starting, opening windows based on the content there, or script checking node name deciding what window to open.

For external triggers, have a Suitelink/OPC (or legacy DDE) client that triggers tags in InTouch that by scripting opens the desired window.

But history has shown me that there are indeed a lot of tricks that are usually on a need-to-know basis, so I can imagine someone else has some experience that is closer to what Olav is asking for.
Or any other view.exe /switch trick that is available.