Futilities/v0.6/clade/Sys/dba/InReq: Difference between revisions
< Futilities | v0.6 | clade | Sys | dba
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
→ {{l/ver/clade|Sys\Events\InputRq|DoList}}<br> | → {{l/ver/clade|Sys\Events\InputRq|DoList}}<br> | ||
→ {{l/ver/clade|Sys\Events\InputRq|DoSetup}}<br> | → {{l/ver/clade|Sys\Events\InputRq|DoSetup}}<br> | ||
→ {{l/ver/clade|Sys\Events\InputRq|DoTest}}<br> | → {{l/ver/clade|Sys\Events\InputRq|DoTest}}<br> | ||
→ {{l/ver/clade|Sys\Events\InputRq|SetFile}}<br> | → {{l/ver/clade|Sys\Events\InputRq|SetFile}}<br> | ||
Revision as of 13:16, 2 August 2025
| Clade Relations | ||
|---|---|---|
| → InReq |
→ DoExport | |
Purpose
Each object encapsulates a given input (request) term (its name, type, and value(s) if any).
Doing Stuff
- To access input arguments, get an appropriate cInRqData object:
$this->OAThisInput()returns the values for just the current request term (used in e.g. Describe()) (THAT WAS THE THEORY, NOT SURE THIS IS CORRECT)static::OAKeptInput()returns the latest set values across all terms (used for doing actions)