• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 13 subscribers
  • Views 23 views
  • Users 0 members are here
Options
Related

WindowMaker modifies application files even if I don't do anything

Federico Fanton

Hi everyone!

I'm very new to InTouch, I've noticed that whenever I open an application with WindowMaker it modifies a lot of the application files right away, even before any modification on my part... For example, the files under Web\DisplayFiles.
Is this normal? Is there a way to disable this behaviour, for example "wait until I save the project before touching anything"?

(I'd like to version control my application using Mercurial or Subversion, but this makes it somewhat harder)

Thanks for your time!

Parents
  • 0

    Frederico - 

    Yes, this is normal - when launching WindowMaker it updates things such as the lok files and some of the internal versioning of the application.  Additionally, most of the files are saved individually when you hit the save button; for example, a script file is changed immediately when you save the script, as opposed to when the program closes.  

    For version control, it may be a better option to use either the Application Publisher tool or the Project Export in Application Manager to create a single application file, and then have something like Tortoise version control that folder as opposed to pointing it directly at the project folder.  This is a safer option than version controlling the individual files, as restoring individual files can risk corruption of the application as a whole. 

    This is the way I handle all my version control for virtually any AVEVA app.  Does it take that extra step to publish/export? sure.  but it ensures that the version of the app is complete. 

    There are other tools such as Octoplant that will version control most of the AVEVA Ops Control products (as well as a good amount of other vendor platforms), but they are of course third party and not necessarily open source like SVN or Mercurial. 

    Hope this helps,

    Phil 

Reply
  • 0

    Frederico - 

    Yes, this is normal - when launching WindowMaker it updates things such as the lok files and some of the internal versioning of the application.  Additionally, most of the files are saved individually when you hit the save button; for example, a script file is changed immediately when you save the script, as opposed to when the program closes.  

    For version control, it may be a better option to use either the Application Publisher tool or the Project Export in Application Manager to create a single application file, and then have something like Tortoise version control that folder as opposed to pointing it directly at the project folder.  This is a safer option than version controlling the individual files, as restoring individual files can risk corruption of the application as a whole. 

    This is the way I handle all my version control for virtually any AVEVA app.  Does it take that extra step to publish/export? sure.  but it ensures that the version of the app is complete. 

    There are other tools such as Octoplant that will version control most of the AVEVA Ops Control products (as well as a good amount of other vendor platforms), but they are of course third party and not necessarily open source like SVN or Mercurial. 

    Hope this helps,

    Phil 

Children
No Data