How Custom Frames Are Handled
Vision marks a frame as "Custom" in the application flow diagram whenever the date of the frame's source code file is more recent than the last time the frame's source code was generated. Be aware that the file's date can change if:
• You edit the file and save your changes.
• You save the file before you leave the editor, even if you have not made any changes.
• VMS: You exit (rather than quit) from the file, even if you have not made any changes. 
• Certain operating system-level changes occur; for example:
– UNIX: You run the touch command on the file. 
– VMS: You assign a new owner to the file. 
Vision does not regenerate the code for a Custom frame when you select Go. You must select the Compile operation in the Application Flow Diagram Editor to force code regeneration of a Custom frame. Vision warns you that compiling the frame can cause any changes that you have made to the source code to be overwritten.
Note: To edit a Vision source code file, use the Edit operation within Vision. Vision marks the frame as Custom when you redisplay the application flow diagram. For more information, see Modifying Vision Code.
When editing a source code file outside of Vision, the Custom frame status indicator does not appear until the next time Vision tries to regenerate the code for the frame (for example, if you change the frame's visual query).
Last modified date: 08/28/2024