I created an inheritable “Master” Project and added a number of Perspective Pages to it. Then I created a non-inheritable “Child” project which inherits from Master. The Child project contains all the Pages present in Master as expected, but then I added more Pages to Master and those additional pages do not get pushed to Child.
Has anyone else seen this issue?
Note that I can add Views to Master and they do get pushed to Child as expected… just the new Pages do not.
I experienced that lately and I whished I had a way to re-sync children with the parent.
Is that something you could think of implementing ? Maybe just a button to force an update, something like that ?
You'd lose anything you've placed into the page configuration of the child. I'm also not 100% sure when the child project's page configuration file is made, so forcing a delete of the page configuration file could result in unforeseen consequences because this is a singleton resource.
Does the project fallback to just using the page configuration of the parent?
If so, does it copy the page configuration of the parent during first reference? When does this happen? Is a restart of the module required in order to replace the missing file?
Does the project fail because it has no page configuration resource at all?
Is it better to replace the page configuration resource with a copy of that of the parent?
Is any of this even possible? Operating systems (primarily Windows) like to prevent deletion of files which are being used by some process - so you might not even be able to delete the file while Ignition is running.
Since I can't recall ever manually deleted the page configuration resource I can't advise you as to the ramifications.