Previous Next        Current Page: NeXtMidas Training / X-Midas Interoperability / XBC / Messages / Unconfigured 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   
  • Sending unconfigured messages to a host primitive:
    • When sending a NeXtMidas message to X-Midas, NeXtMidas will automatically convert the NeXtMidas message to an X-Midas message.
      • The data in the NeXtMidas message should be a Table.
      • The table needs the following keys:
        ARGS Number of arguments.
        TYPE The X-Midas argument type specifier (e.g. "LLA").
        VAL1 The 1st value.
        VAL2 The 2nd value.
            :     :
        VALN The Nth value.
        • Example: 
          message send echoid SPAM SPAM ^info {TYPE="LLA",ARGS="3",&
  VAL1=^lval1,VAL2=^lval2,VAL3="^mystr"}
  • Receiving an unconfigured message from a host primitive:
    • The message will be similar to the message sent (with VAL1, VAL2, ... VALN) but without the TYPE and ARGS fields.
back