Previous Next        Current Page: NeXtMidas Training / X-Midas Interoperability / XBC / Messages
back
+ Start Here   
+ Background   
+ Common Midas Concepts   
+ Getting Started - Part 1   
+ Getting Started - Part 2   
+ Working with Files   
+ Option Trees   
+ Macros - Part 1 (Basics)   
+ Macros - Part 2 (Graphics)   
+ NetBeans - Part 1 (Setup)   
+ NetBeans - Part 2 (GUIs)   
+ NetBeans - Part 3 (Profiler)   
+ Eclipse - Part 1 (Setup)   
+ Eclipse - Part 2 (GUIs)   
+ Primitives   
+ WebStart   
+ Maps & Imagery   
- X-Midas Interoperability   
   + Overview   
   - XBC   
      - XBC Setup   
      - Adding Host Primitives   
      - Messages   
         - Configured Messages   
         - Unconfigured Messages   
   + Lab 1   
   + NeXtOpt   
+ RMIF & Remoting   
+ Installing NeXtMidas   
+ Support & Maintenance   
+ File Handlers   


  • Notes about X-Midas messages:
    • NeXtMidas does not deal with "configured" and "unconfigured" messages the same way X-Midas does.
      • In NeXtMidas messages, the data can be any object (frequently a Table) without any specific configuration.
      • X-Midas messages are structured byte buffers that either match a pre-defined configuration (configured) or are defined ad hoc (unconfigured).
X-Midas Users Take Note:
Since host primitives are unable to handle NeXtMidas ID's (which are strings) all messages from a host primitive will be sent to the same location as specified by the /MSGID= switch passed to the host primitive. By default /MSGID= is set to null, to see the messages in the processMessage procedure of a macro use /MSGID=MAIN.
(This applies to XBC only, not NeXtOpt.)

back