I finally got the menu system working. But I ran into a glitch when using Save As.
Interface Assets are saved local to the project. When saving to another project name, I believe the assets are likewise brought forward (to the new project file directory), but I think the internal pointers for the interface assets got corrupted.
Result - I could use the assets, but I could not edit them from within IF. The file name looked like a concatenation of the original file path and the new file path.
I resolved by recreating a new set of interface assets.
But in conjunction with version control (I’ll send in a separate topic), I think one or more of the following would be useful:
Allow user control over the file directory / name of an interface asset.
Allow user to repoint an interface asset to another physical file (this could cause corruption if formats are not identical).
Allow original files to be used and allow these files to be stored outside the project file directory.
- the current model of replicating the files is confusing.
- with the current model, there’s no way to auto-update content changes. If you’re working with a master excel database, you have to replicate to the local version within IF.
Eventually, you’ll need to extend the interface function to support RDBMS’. So the notion of external data sources outside of IF seems like a logical direction.