AMX TPI-PRO-4, Operation/Reference Manual

Page: 127 / 218

NetLinx Programming
121 TPI-PRO/DVI (Total Presentation Interface)
Button Query Commands
Button Query commands reply back with a custom event. There will be one custom event for each button/state
combination. Each query is assigned a unique custom event type.
The following example is for debug purposes only:
NetLinx Example: CUSTOM_EVENT[device, Address, Custom event type]
DEFINE_EVENT
CUSTOM_EVENT[TP,529,1001] // Text
CUSTOM_EVENT[TP,529,1002] // Bitmap
CUSTOM_EVENT[TP,529,1003] // Icon
CUSTOM_EVENT[TP,529,1004] // Text Justification
CUSTOM_EVENT[TP,529,1005] // Bitmap Justification
CUSTOM_EVENT[TP,529,1006] // Icon Justification
CUSTOM_EVENT[TP,529,1007] // Font
CUSTOM_EVENT[TP,529,1008] // Text Effect Name
CUSTOM_EVENT[TP,529,1009] // Text Effect Color
CUSTOM_EVENT[TP,529,1010] // Word Wrap
CUSTOM_EVENT[TP,529,1011] // ON state Border Color
CUSTOM_EVENT[TP,529,1012] // ON state Fill Color
CUSTOM_EVENT[TP,529,1013] // ON state Text Color
CUSTOM_EVENT[TP,529,1014] // Border Name
CUSTOM_EVENT[TP,529,1015] // Opacity
{
Send_String 0,"'ButtonGet Id=',ITOA(CUSTOM.ID),' Type=',ITOA(CUSTOM.TYPE)"
Send_String 0,"'Flag =',ITOA(CUSTOM.FLAG)"
Send_String 0,"'VALUE1 =',ITOA(CUSTOM.VALUE1)"
Send_String 0,"'VALUE2 =',ITOA(CUSTOM.VALUE2)"
Send_String 0,"'VALUE3 =',ITOA(CUSTOM.VALUE3)"
Send_String 0,"'TEXT =',CUSTOM.TEXT"
Send_String 0,"'TEXT LENGTH =',ITOA(LENGTH_STRING(CUSTOM.TEXT))"
}
All custom events have the following 6 fields:
These fields are populated differently for each query command. The text length (String Encode) field is not
used in any command.
Custom Event Fields
• Field: Description
• Uint Flag: 0 means text is a standard string, 1 means Unicode encoded string
• slong value1: button state number
• slong value2: actual length of string (this is not encoded size)
• slong value3: index of first character (usually 1 or same as optional index
• string text: the text from the button
• text length (string encode): button text length