Differences

This shows you the differences between two versions of the page.

--- visual3d:tutorials:pipeline:meta_command_creation [2024/06/26 20:31] – created sgranger
+++ visual3d:tutorials:pipeline:meta_command_creation [2025/07/09 18:16] (current) – sgranger
@@ Line 1: / Line 1: @@
-====== Meta_Command_Creation ======
+====== Meta Command Creation ======
 ==== Combining Pipeline Scripts into a Meta-Command ====
@@ Line 5: / Line 5: @@
 This is an example for creating a meta-command in Visual3D.
-. Suppose you have a pipeline script that generates a metric or some sort of result.
+  - Suppose you have a pipeline script that generates a metric or some sort of result.
+  - Suppose also, that you have a second script that needs the result of the first script.
+  - Finally suppose you are tired of calling two scripts and want to do it all at once
-. Suppose also, that you have a second script that needs the result of the first script.
+Here is an extremely simplistic example: \\
+Script1 below prompts you to enter a number, and Script2 prints it out. \\
-. Finally suppose you are tired of calling 2 scripts and want to do it all at once.
-\\
-Here is an extremely simplistic example. Script1 below prompts you to enter a number, and script2 prints it out.
-(Note: Naturally, these scripts will not run separated like this – the input value would have to be stored somewhere. Using a Call_Script command also fails because it does not pass data.)
-\\
+**Note:** Naturally, these scripts will not run separated like this – the input value would have to be stored somewhere. Using a Call_Script command also fails because it does not pass data.
 <code>
@@ Line 26: / Line 21: @@
  ;
 </code>
-\\
 <code>
@@ Line 39: / Line 31: @@
 </code>
-Here is a process to modify the scripts so that they work together:\\
+Here is a process to modify the scripts so that they work together:
+  - Convert the second script to a meta-command
+  - Save the new meta-command in the proper Visual3D directory
+  - Edit the first script to call the meta-command
-  - Convert the second script to a meta-command\\
+Edit **Script2.v3s** and change it to the following, and save it as **number_game.v3m**. \\
+Note that the meta-command syntax is simply a few lines as a header, and then changing any input parameter names to match. For the syntax of the header see [[Visual3D:Documentation:Pipeline:Meta_Commands:Meta_Commands_Overview|Pipeline_Commands:Meta_Commands]].
-  - Save the new meta-command in the proper Visual3D directory\\
-  - Edit the first script to call the meta-command\\
-\\
-Edit **Script2.v3s** and change it to the following, and save it as **number_game.v3m**. //Note that the meta-command syntax is simply a few lines as a header, and then changing any input parameter names to match. For the syntax of the header see [[Visual3D:Documentation:Pipeline:Meta_Commands:Meta_Commands_Overview|Pipeline_Commands:Meta_Commands]].//
 <code>
@@ Line 67: / Line 55: @@
 </code>
-Copy the file **number_game.v3m** to the meta-command directory: Possibly: C:\Program Files (x86)\Visual3D v5\ Plugins\Meta-Commands
+Copy the file **number_game.v3m** to the meta-command directory: Possibly: C:\Program Files (x86)\Visual3D v5\ Plugins\Meta-Commands \\
-\\
 Edit **Script1.v3s** and change it to the following:
@@ Line 84: / Line 70: @@
 </code>
-That’s it. Restart Visual3D and run the new **script1.v3s**.
+That’s it. Restart Visual3D and run the new **script1.v3s**. \\
 Note also that if you copy script1.v3s to C:\Program Files (x86)\Visual3D v5\Plugins\Scripts then the script will show up in the box on the workspace tab in Visual3D for easy access.