Difference between revisions of "APT:ReceiveParameter"
Jump to navigation
Jump to search
| Line 76: | Line 76: | ||
|- | |- | ||
| 0x3 | | 0x3 | ||
| − | | | + | | Launched library applet finished loading |
| + | |- | ||
| + | | 0xA | ||
| + | | Launched library applet closed | ||
|- | |- | ||
| 0xB | | 0xB | ||
Revision as of 03:27, 20 November 2014
Request
| Index Word | Description |
|---|---|
| 0 | Header code [0x000D0080] |
| 1 | AppID |
| 2 | Parameter buffer size, max size is 0x1000(this can be zero). |
The following is located 0x100-bytes after the beginning of the above command buffer:
| Index Word | Description |
|---|---|
| 0 | (Size<<14) | 2 |
| 1 | Output parameter buffer ptr |
Response
| Index Word | Description |
|---|---|
| 0 | Header code |
| 1 | Result code |
| 2 | AppID of the process which sent these parameters. |
| 3 | Signal type |
| 4 | Actual parameter buffer size, this is <= to the the input size. |
| 5 | Value 0x10 |
| 6 | Handle from the source process which set the parameters, this handle is likely used for shared memory(this can be 0x0). |
| 7 | (Size<<14) | 2 |
| 8 | Output parameter buffer ptr |
Description
This returns the current parameter data from NS state, from the source process which set the parameters. Once finished, NS will clear a flag in the NS state so that this command will return an error if this command is used again if parameters were not set again. This is called when the second Initialize event is triggered. It returns a signal type indicating why it was triggered.
| Type | Description |
|---|---|
| 0x1 | Application just started |
| 0x3 | Launched library applet finished loading |
| 0xA | Launched library applet closed |
| 0xB | Returned to application |
| 0xC | Exiting application |
| 0xF | ? |