- Notes about X-Midas messages:
  - An X-Midas macro can send messages to any of the NeXtMidas macros or primitives launched from it.
    - The command must have an X-Midas-compatible numeric `/ID=`.
    - If the X-Midas macro launches a NeXtMidas macro, it can send messages to that macro, but not any commands in that macro (this is standard for NeXtMidas).
    - It is very common to increase the X-Midas default message queue size of 512 (8 byte) slots using the /NMQ= switch on the `startmacro` or the `message up` line, e.g.
      `startmacro/nmq=8k`
      --OR--
      `message/nmq=8k up`
  - NeXtMidas commands can send messages to the X-Midas macro and/or primitives.
    - From a NeXtMidas macro, use the `MESSAGE` command (more on this in the next section).
    - From a NeXtMidas primitive, use the `sendMessage(Message msg)` protected API inherited from the `Command` class which will use the automatically parsed `/MSGID=` switch to specify the target of sent messages. (Since NeXtMidas 2.7.1)
  - There are three categories of messages supported:
    - Configured X-Midas Messages
    - Un-Configured X-Midas Messages
    - "Translated" NeXtMidas Messages (Since NeXtMidas 2.7.1)

Don't Make This Mistake:
Increasing the X-Midas message queue size (via the `/NMQ=` switch) is required when using automatically "Translated" NeXtMidas Messages, since one `/NM/` message is typically 540 slots.