| Using Simulink | |
Opening Models with Different Character Encodings
If you open a model created in a MATLAB session configured to support one character set encoding, for example, Shift_JIS, in a MATLAB session configured to support another character encoding, for example, US_ASCII, Simulink displays a warning or an error message, depending on whether it can or cannot encode the model, using the current character encoding, respectively. The warning or error message specifies the encoding of the current session and the encoding used to create the model. To avoid corrupting the model (see Saving Models with Different Character Encodings) and ensure correct display of the model's text, you should
slCharacterEncoding command to change the character encoding of the current MATLAB session to that of the model as specified in the warning message.
You can now safely edit and save the model.
Avoiding Initial Model Open Delay
You may notice that the first model that you open in a MATLAB session takes longer to open than do subsequent models. This is because to reduce its own startup time and to avoid unnecessary consumption of your system's memory, MATLAB does not load Simulink into memory until the first time you open a Simulink model. You can cause MATLAB to load Simulink at MATLAB startup, and thus avoid the initial model opening delay, using either the -r MATLAB command line option or your MATLAB startup.m file to run either load_simulink (loads Simulink) or simulink (loads Simulink and opens the Simulink Library browser) at MATLAB startup. For example, to load Simulink at MATLAB startup on Microsoft Windows systems, create a desktop shortcut with the following target:
Similarly, the following command loads Simulink at MATLAB startup on UNIX systems:
| | Starting Simulink | Simulink Editor | |
© 1994-2005 The MathWorks, Inc.