visual3d:documentation:pipeline:file_commands:exit_workspace
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:pipeline:file_commands:exit_workspace [2024/06/26 20:05] – removed sgranger | visual3d:documentation:pipeline:file_commands:exit_workspace [2025/07/08 18:25] (current) – wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Exit Workspace ====== | ||
+ | |||
+ | ===== Overview ===== | ||
+ | |||
+ | The **Exit_Workspace** command is used to close the Visual3D application. It is commonly used as the final step in batch processing pipelines, especially when Visual3D needs to be shut down after executing a series of commands, or when preparing to reload the application with a different dataset. | ||
+ | * This command is located in the **File Management** folder within the pipeline interface. | ||
+ | * The workspace is not saved automatically when this command is executed, therefore any changes must explicitly saved before using. | ||
+ | |||
+ | ===== Pipeline Command ===== | ||
+ | The command below is as seen on the Visual3D application, | ||
+ | |||
+ | < | ||
+ | Exit Workspace | ||
+ | |||
+ | ; | ||
+ | </ | ||
+ | |||
+ | ===== Command Parameters + Dialog ===== | ||
+ | |||
+ | No dialog box or customization options are available. It simply exits the Visual3D application. | ||
+ | |||
+ | ===== Examples ===== | ||
+ | The following example will go through the use of the Exit_Workspace command in the Visual3D application. | ||
+ | |||
+ | ==== Example 1: Save a File after applying Gait Events, then exit Visual3D ==== | ||
+ | |||
+ | This pipeline demonstrates how to use **Exit_Workspace** as the final step after loading a file, processing it with automatic gait events, saving the changes to a new CMZ file and then exiting the application. | ||
+ | |||
+ | Step 1 is to open the Visual3D application and execute the first command which will open a CMZ file of your choice, the path must be entered into the /FILE_NAME parameter. Make sure to choose a file which does not contain automatically detected gait events yet. | ||
+ | |||
+ | < | ||
+ | File_Open | ||
+ | / | ||
+ | ! /FILE_PATH= | ||
+ | ! / | ||
+ | ! /SUFFIX= | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | Step 2 is to execute the " | ||
+ | |||
+ | < | ||
+ | Automatic_Gait_Events | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | Step 3 is to execute the File Save As command to save this file with the automatically detected gait events. The path of the export must be entered into the /FILE_NAME parameter. | ||
+ | |||
+ | < | ||
+ | File_Save_As | ||
+ | /FILE_NAME= "&:: | ||
+ | ! /FOLDER= | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | Step 4 is to execute the File_New command in order to make sure the workspace has been cleared and no leftover data is available. | ||
+ | |||
+ | < | ||
+ | File_New | ||
+ | |||
+ | ; | ||
+ | </ | ||
+ | |||
+ | Step 5, the final step, is to use the command which this page is based on, Exit_Workspace, | ||
+ | |||
+ | < | ||
+ | Exit_Workspace | ||
+ | |||
+ | ; | ||
+ | </ | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | [[Visual3D: | ||
+ | |||
+ | |||
visual3d/documentation/pipeline/file_commands/exit_workspace.1719432314.txt.gz · Last modified: 2024/06/26 20:05 by sgranger