Page 902 - ExtendSim User Guide
P. 902

876
Cross-Platform Considerations
Transferring files between operating systems
converts model files when they are opened on a different platform. If you program your own blocks, the ExtendSim for Mac OS package includes a file conversion utility which you can use to convert libraries and picture resource extensions from one operating system format to another. Other extensions that you build, such as QuickTime movies, DLLs, and Shared Libraries require more extensive conversion. Include files are, of course, already cross-plat- form compatible.
Model files
The Windows version of ExtendSim can read ExtendSim model files created on the Mac OS as long as the name format is correct, as discussed above. The Mac OS version of ExtendSim can read ExtendSim model files created under Windows without file name modification (in fact, as discussed in the Note above, the MOX extension should not be removed.) When you open a model file that was created on another operating system, ExtendSim will notify you that it is converting the file from that system to the current one. Once you save the model file, it will be in the format of your current operating system.
If your models (including hierarchical blocks) use libraries that you have created yourself, and you have changed the name of those libraries, ExtendSim will not be able to locate the library. In this case, ExtendSim will ask you to find and select the correct library as described in “Searching for libraries and blocks” on page 567. Keeping all your libraries in the Libraries folder will make this search process easier. Saving the model will cause the new libraries to be used from then on.
For model files that have blocks that access text files (such as the Read block from the Value library), you may need to change the name of the text file that is being read to conform to plat- form requirements, as discussed above. Be sure to also change the name of the file in the Read block’s dialog to correspond to the new file name.
☞ The first time you run a model that has been transferred from one operating system to another, any Equation blocks in the model will recompile to the format of the new system at the begin- ning of the simulation run. Messages that report this process may appear too quickly for you to read.
Hierarchical blocks in libraries
If you have a hierarchical block saved in a library and you have renamed any of the libraries of the blocks inside the hierarchical block (for example, to comply with Windows format), you need to update the hierarchical block’s information so that it can locate the renamed libraries. The easiest way to do this is to drag hierarchical blocks from their libraries, place them on a worksheet, and update their structure, as discussed below.
☞ This is only required for hierarchical blocks saved in libraries; hierarchical blocks saved only in a model get updated with the model.
When you add a hierarchical block from a library to a model worksheet, the hierarchical block causes ExtendSim to open the libraries of the blocks inside it. Since you have renamed those libraries, ExtendSim will not be able to locate them. In this case, ExtendSim will ask you to find and open the correct libraries. Note: keeping all your libraries in the Libraries folder will make this search process easier.
If you save the model worksheet that contains the hierarchical block, the location of the renamed libraries is saved for the model only. Before you close the model worksheet, you also need to update the hierarchical block’s library information. To do this, open the hierarchical block’s structure window and then close it, causing the hierarchical block’s Save dialog to
Appendix


































































































   900   901   902   903   904