• State Verified Answer
  • Replies 3 replies
  • Subscribers 10 subscribers
  • Views 561 views
  • Users 0 members are here
Options
Related

Latest added window not found after deployed Intouch Application?

Jakob Tislevoll

We have added several windows in Windowmaker, let's call them "A, B and C".

In Window "A, B, and C" we load an Industrial graphic with the same names "A, B and C".

Within the Industrial Graphics, we have navigation buttons using "SYS_NAV_Window_Select", and point them to "A, B and C".

We deploy from IDE, and open the application using either WindowViewer, og via Application Manager. Using the navigation buttons, the correct windows "A, B and C" open.

Then we made a new Industrial Graphic, "D", and a new corresponding Window in WindowMaker called "D". Same procedure, we use "SYS_NAV_Window_Select" and enter "D".

Now, if we open the Application using WindowViewer or Application Manager, we can not open window "D", and the logger says "No such Window: "D"".

This happens on both GR and remote clients.

The only way to make the application behave correctly and find window "D", is to open it using the "Runtime" button in WindowMaker. Then, it recognizes the window name.

It seems like there is an issue loading changes into the application from deployment, or a maximum number of windows? Please ask any questions for clarification, we have not had this problem before.

Parents
  • +1

    Hi Jakob!

    Sounds like you have encountered a interesting bug, There should not be a maximum number of windows for use in InTouch.

    What version of System Platform are you running?

    On the remote node/the deployed application folder, please review the file ww_wdws.ndx. this file contains the references between window-names and the corresponding .win file.

    It would be very interesting to see if the missing window is listed here, also if the .win file is part of the distribution/deploy.

    You mention that it is a Deployed application so I assume that you are using InTouch as a managed application, the source application, and the version that you run when pressing 'Runtime' from Development will then be CheckedOut folder, 

    C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<YourGalaxy>\ObjectFileStorage\$MyApp\CheckedOut

    compare the file with the CheckedIn folder, this is the folder that is distributed when deployed.

    If all above seems ok, then it would be interesting to see in what way you are opening the windows. (using show symbol script, InTouch show window animation, or InTouch show script since I'm not familiar with any native function named SYS_NAV_Window_Select.

    Or is it a message tag that is used in a Datachange script?

  • 0 in reply to Richard Köhlerstrand

    Thank you very much for such a detailed response, Richard!

    It got us thinking in the right direction, and after checking the folders suggested, we could determine that it was in fact a mismatch and a failure to save the latest made windows.

    I almost wish the solution would be more complicated, but it turned out we were editing a derived instance of the ViewApp, and so our changes did not make it to the "CheckedIn" folder. Once we edited the ViewApp highest in the derivation, the changes stuck and we were good.

Reply
  • 0 in reply to Richard Köhlerstrand

    Thank you very much for such a detailed response, Richard!

    It got us thinking in the right direction, and after checking the folders suggested, we could determine that it was in fact a mismatch and a failure to save the latest made windows.

    I almost wish the solution would be more complicated, but it turned out we were editing a derived instance of the ViewApp, and so our changes did not make it to the "CheckedIn" folder. Once we edited the ViewApp highest in the derivation, the changes stuck and we were good.

Children
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.