Scott,
> There are no ideal hooks to do this. The only callback that could
be
> used is SequenceFileUnload, but each sequence file would have to
> define the callback and invoke a tool in a shared sequence file.
You
> would probably want to use PropertyObjectFile.ChangeCount to
determine
> if the files was modified since it was loaded and only do your
> checking if true. Minimally you could warn the user if something
was
> not correct when the file was unloaded from memory.
Thanks. The SequenceFileUnload option isn't really a viable fix for
this problem as as I run into the same problem as the Tools menu item:
the users will forget to add the callback to their sequence files. I
was hoping there was some other hook I was missing.
On a related note, is th
ere a repository for "wish list" items for
future versions of TestStand? The big "wish list" feature I think
would benefit all (not to mention solve my problem 😉 would be the
ability to create a new sequence file from a template (so new sequence
files can be "preloaded" with specific FileGlobals, Locals,
implemented callbacks, etc).
Thanks,
---
Bob