Add Process/enig start ingress/egress bytes stats

This commit is contained in:
Bryan Ashby
2022-08-01 23:09:18 -06:00
parent 044cc24418
commit 715202680e
10 changed files with 51 additions and 0 deletions

View File

@@ -109,6 +109,8 @@ There are many predefined MCI codes that can be used anywhere on the system (pla
| `NP` | Count of new private mail to the current user |
| `IA` | Indicator as to rather the current user is **available** or not. See also `getStatusAvailIndicators()` in [Themes](themes.md) |
| `IV` | Indicator as to rather the curent user is **visible** or not. See also `getStatusVisibleIndicators()` in [Themes](themes.md) |
| `PI` | Ingress bytes for the current process (since ENiGMA started up) |
| `PE` | Egress bytes for the current process (since ENiGMA started up) |
Some additional special case codes also exist:

View File

@@ -96,6 +96,8 @@ The following MCI codes are available:
* `newMessagesAddrTo`: Number of new messages **addressed to the current user**.
* `availIndicator`: Is the current user availalbe? Displayed via `statusAvailableIndicators` or system theme. See also [Themes](../art/themes.md).
* `visIndicator`: Is the current user visible? Displayed via `statusVisibleIndicators` or system theme. See also [Themes](../art/themes.md).
* `processBytesIngress`: Ingress bytes since ENiGMA started.
* `processBytesEgress`: Egress bytes since ENiGMA started.
> :information_source: While [Standard MCI](../art/mci.md) codes work on any menu, they will **not** refresh. For values that may change over time, please use the custom format values above.