commands
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
commands [2024/11/22 07:54] – steve | commands [2024/11/22 13:18] (current) – steve | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Commands ====== | + | ===== Commands ===== |
- | holding page to contain explanation | + | |
+ | ==== copy to the control | ||
+ | |||
+ | **__copy | ||
+ | |||
+ | ==== delete to the control==== | ||
+ | |||
+ | **__delete to the control__** = copy the clicked background template to replace the existing control template. The background template will then be deleted from the storage box and from the .box file. The control template must be stored again at some stage if it is to remain a part of the track plan. | ||
+ | |||
+ | ==== make the control ==== | ||
+ | **__make the control__** = store the existing control template, then as delete to the control. This is simply for convenience if you know you are going to first store the control template and then delete another one to the control. With make the control Templot does both functions in one go -- this is handy to swap between two or more templates when for example shoving timbers or adjusting check rails, and when working with partial templates. | ||
+ | |||
+ | ==== wipe to the control ==== | ||
+ | **__wipe to the control__** = copy the clicked background template to replace the existing control template. The background template will then become an unused template. It remains in the storage box and the .box file, but it is not visible on the trackpad. As an unused template it can be easily restored to use if you find that you need it later. | ||
- | ===== copy to the control ===== | ||
- | The assumption is that you are going to move the control template, | ||
commands.1732262094.txt.gz · Last modified: 2024/11/22 07:54 by steve