User Tools

Site Tools


en:tutorials:command:using_the_command_module

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:tutorials:command:using_the_command_module [2020/08/31 06:54 (5 years ago)] – ↷ Page moved from en:tutorials:community:sausage:using_the_command_module to en:tutorials:command:using_the_command_module sausageen:tutorials:command:using_the_command_module [2024/11/26 19:46 (4 months ago)] (current) – Broken link sausage
Line 7: Line 7:
 1. The Command Module provides a **__Console__** that allows you to enter commands to manipulate Objects, the Config, and other parts of the Orx system without having to change your code, or your config, and without having to recompile/re-run. It allows you to do a "dress rehearsal" of Object positions, alpha, or any other parameter in realtime to see the effect of a change instantly. The Console can be considered somewhat similar to Immediate Mode in Visual Studio, or even Direct Mode in the old Amiga AMOS programming environment. 1. The Command Module provides a **__Console__** that allows you to enter commands to manipulate Objects, the Config, and other parts of the Orx system without having to change your code, or your config, and without having to recompile/re-run. It allows you to do a "dress rehearsal" of Object positions, alpha, or any other parameter in realtime to see the effect of a change instantly. The Console can be considered somewhat similar to Immediate Mode in Visual Studio, or even Direct Mode in the old Amiga AMOS programming environment.
  
-2. The Command Module presents a **__Command Syntax__**. What you enter into the Console can be taken and used to build Tracks. Tracks are groups of manipulations to objects or config at set time intervals. Without tracks, chaining lots of effects in a sequence would otherwise have be managed by variables and events, which can become complex and messy. Tracks will be dealt with in the [[en:tutorials:community:sausage:tracks|Tracks article]].+2. The Command Module presents a **__Command Syntax__**. What you enter into the Console can be taken and used to build Tracks. Tracks are groups of manipulations to objects or config at set time intervals. Without tracks, chaining lots of effects in a sequence would otherwise have be managed by variables and events, which can become complex and messy. Tracks will be dealt with in the [[en:tutorials:tracks:tracks|Tracks article]].
  
 This article will cover how to use the command syntax in the Command Module's Console, and how to perform manipulations. This article will cover how to use the command syntax in the Command Module's Console, and how to perform manipulations.
Line 13: Line 13:
 ==== Starting with a basic project ==== ==== Starting with a basic project ====
  
-If you don't have a basic project to work with, head over to [[en:tutorials:community:sausage:using-premake-for-your-own-project|here]] to set one up. +If you don't have a basic project to work with, head over to [[en:tutorials:projects:creating_your_own_project|here]] to set one up. 
  
 Define a sprite object in your config: Define a sprite object in your config:
Line 121: Line 121:
 </code> </code>
  
-Now that you know a little about the command syntax, let's try [[en:tutorials:community:sausage:tracks|using these command sequences in a track]] and call it from code.+Now that you know a little about the command syntax, let's try [[en:tutorials:tracks:tracks|using these command sequences in a track]] and call it from code.
  
en/tutorials/command/using_the_command_module.1598882081.txt.gz · Last modified: 2020/08/31 06:54 (5 years ago) by sausage