Class ManualToolingCommand
- Namespace
- Hi.SessionCommands
- Assembly
- HiNc.dll
Command that puts a tool of the tool house in the spindle the way the
operator loads one by hand: no tool-change travel, no machining step, no
program played and no file number taken. The mission-list form of
PlayToolingTeleport(int), for a program written
for a hand-changed tool (no T… M06): placed before the program's
NcFileCommand, which then keeps its lines and its file number
(an NcCodeCommand holding the change would play as a file of
its own and take a number). It applies no tool length — the program's
G43 H or the work offset's Z carries it, as on the machine; a length
left out puts the tip a whole tool length below every programmed Z, so the
play either touches nothing (Play-Touch–None on the shell) or
plunges that far into the stock, and where another tool of the play did
touch, the tool that did not is named by Tool-Touch–None on the
step sink. A ToolId
below 1 (the fresh command's 0) mounts nothing and says
ManualTooling-Command–NoToolId on the shell; an id the house lacks
says Tooling–NotFound and leaves the spindle empty, a tool without a
cutter Tooling–NoCutter. The spindle keeps the tool until the next
tooling act or the reset.
[CultureText("zh-Hant", "手動裝刀")]
[CultureText("zh-Hans", "手动装刀")]
[CultureText("vi", "Lắp dao thủ công")]
[CultureText("ja", "手動工具装着")]
[CultureText("zh-Hant", "換刀", Key = "Tool Change")]
[CultureText("zh-Hans", "换刀", Key = "Tool Change")]
[CultureText("vi", "Thay dao", Key = "Tool Change")]
[CultureText("ja", "工具交換", Key = "Tool Change")]
[CommandCatalog(CommandCategory.Program, Order = 1, Aliases = new string[] { "Tool Change" })]
public class ManualToolingCommand : ITitleCommand, ISessionCommand, IMakeXmlSource
- Inheritance
-
ManualToolingCommand
- Implements
- Inherited Members
- Extension Methods
Constructors
ManualToolingCommand()
Default constructor: no tool named (ToolId 0).
public ManualToolingCommand()
ManualToolingCommand(XElement, string)
Ctor. An absent ToolId element keeps the default.
public ManualToolingCommand(XElement src, string baseDirectory)
Parameters
Fields
ConstDisplayName
The command's own name — the DisplayNameAttribute value, the localization key, AND the word GetCommandTitle(ICommandTextSource) leads with.
public const string ConstDisplayName = "Manual Tooling"
Field Value
Properties
ToolId
Tool-house id of the tool the operator loads; the house numbers its
tools 1 and above. 0, the default, names none: the command then mounts
nothing and says ManualTooling-Command–NoToolId when it runs, and
the program's first feed move says Step-Tool–NotEquipped — two
pointers at the same fix, never a silently guessed tool.
[CultureText("zh-Hant", "刀號", Key = "Tool Id")]
[CultureText("zh-Hans", "刀号", Key = "Tool Id")]
[CultureText("vi", "Số dao", Key = "Tool Id")]
[CultureText("ja", "工具番号", Key = "Tool Id")]
public int ToolId { get; set; }
Property Value
XName
Name for XML IO.
public static string XName { get; }
Property Value
Methods
GetCommandTitle(ICommandTextSource)
Gets the title of the command — one row in a command list or a mission tree — composed from the caller's vocabulary: the command owns the composition and degradation rules, the caller owns the language.
The shape is Name, or Name [detail] once there is a
detail worth showing. The NAME always leads and is never dropped:
a row must say WHAT it is even when the detail is a title the user
wrote, otherwise a newcomer cannot tell a command list from a
script. The detail trails because these rows truncate from the
right. An empty detail takes the bare-name form rather than
rendering dangling brackets.
public string GetCommandTitle(ICommandTextSource text)
Parameters
textICommandTextSourceCulture-bearing vocabulary the static words are taken from.
Returns
- string
The command title.
MakeXmlSource(string, string, bool)
Creates an XML representation of the object. This method may also generate additional resources such as related files.
public XElement MakeXmlSource(string baseDirectory, string relFile, bool exhibitionOnly)
Parameters
baseDirectorystringThe base directory for resolving relative paths
relFilestringThe relative file path for the XML source
exhibitionOnlyboolif true, the extended file creation is suppressed.
Returns
- XElement
An XML element representing the object's state
Remarks
For the demand of easy moving source folder (especially project folder) without configuration file path corruption, the relative file path is applied.
The baseDirectory is typically the folder at the nearest configuration file folder.
Since the folder can be moving with the configuration file.
Reg(XFactory)
Registers this type's deserializer with the given XFactory
(or Default when factory is
null). Idempotent.
public static void Reg(XFactory factory = null)
Parameters
factoryXFactory
Run(SessionShell)
Runs the command, delegating execution to the provided session shell.
public IEnumerable<Action> Run(SessionShell sessionShell)
Parameters
sessionShellSessionShellSession shell that exposes the machining facade to commands.
Returns
- IEnumerable<Action>
Sequence of actions to be executed. A command may do its work as it is enumerated and yield
nullbetween the pieces of it. The player invokes each action in order and paces after it – a Pause holds there, jobs queued for the run's pace point run there, and a Stop of its run ends the run there – and it ends a stopped run at anullitem too, and before the next row of a ListCommand. An action is not checked for a Stop before it runs: one handed over after the Stop runs, and the run ends at the pace after it. Where the run ends, the player disposes the enumeration: the command's code after that item does not run, and what must run whatever happens belongs in afinallyof the iterator. An exception that leaves the enumeration while the run is live ends the run as a fault: the player reports it asPlayer-Run–Fault, the run ends there as not finished, and no later row of a ListCommand runs; a command that catches and reports its own failure (a ScriptCommand‘sScriptCommand-Run–Fault, the CSV mapping commands’Map-SingleCsv–FaultandMap-SeriesCsv–Fault) lets the mission go on. Once the run is stopped, whatever leaves the enumeration – the run's own cancellation, or an exception its unwinding throws – is the Stop, and no message is said for it. A command that catches and reports its own failure still says it after the Stop: a ScriptCommand reports any exception other than a cancellation that comes out of its script's body – the body's own, or one the stopped run's unwinding throws inside the body – asScriptCommand-Run–Fault, and the CSV mapping commands' catches let a cancellation through alone; the stopped run then starts no later row.