Ferreteria/v0.6/clade/Sys/Events/InputRq/Setting: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(changing relationships; renaming) |
||
| Line 4: | Line 4: | ||
|- | |- | ||
| align=right | {{l/ver/clade|Sys/Events|InputRq}} | | align=right | {{l/ver/clade|Sys/Events|InputRq}} | ||
| → {{l/ver/clade|Sys\Events\InputRq| | | → {{l/ver/clade|Sys\Events\InputRq|Setting}} | ||
|} | |} | ||
==Functions== | ==Functions== | ||
Revision as of 13:09, 1 September 2025
| Clade Family | ||
|---|---|---|
| InputRq | → Setting | |
Functions
public
function Describe() : string(override)function Go()(override)function NameOfInput() : string
internal
function ParseInputString(string $s) : void$s= first value given to the subcommand (e.g. for "cmd:stuff:things", $s will be "stuff")- Additional parts (e.g. "things") get sent to ParseInputArgs().
function ParseInputArgs(array $arArgs) {} : no code$arArgs= number-based array of additional values (if any) (e.g. for "cmd:stuff:things:more", $arArgs will be [0]=>"things", [1]=>"more)- By default, these aren't retained since their meaning is action-dependent. Podlings can override this.