Table of Contents
Advertisement
Button Query Commands
Button Query commands reply with a custom event. Each button/state combination has one custom event.
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]
CUSTOM_EVENT[TP,529,1002]
CUSTOM_EVENT[TP,529,1003]
CUSTOM_EVENT[TP,529,1004]
CUSTOM_EVENT[TP,529,1005]
CUSTOM_EVENT[TP,529,1006]
CUSTOM_EVENT[TP,529,1007]
CUSTOM_EVENT[TP,529,1008]
CUSTOM_EVENT[TP,529,1009]
CUSTOM_EVENT[TP,529,1010]
CUSTOM_EVENT[TP,529,1011]
CUSTOM_EVENT[TP,529,1012]
CUSTOM_EVENT[TP,529,1013]
CUSTOM_EVENT[TP,529,1014]
CUSTOM_EVENT[TP,529,1015]
{
SEND_STRING 0,"'ButtonGet Id=',ITOA(CUSTOM.ID),' Type=',ITOA(CUSTOM.TYPE)"
Send_String 0,"'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
Send_String 0,"'TEXT LENGTH =',ITOA(LENGTH_STRING(CUSTOM.TEXT))"
}
All custom events have the following 6 fields:
Custom Event Fields
Field
Uint Flag
slong value1
slong value2
slong value3
string text
text length (string encode)
These fields are populated differently for each query command. The text length (String Encode) field is not
used in any command.
NXD-430/NXD-435 4.3" Wall/Flush Mount Touch Panels
// Text
// Bitmap
// Icon
// Text Justification
// Bitmap Justification
// Icon Justification
// Font
// Text Effect Name
// Text Effect Color
// Word Wrap
// ON state Border Color
// ON state Fill Color
// ON state Text Color
// Border Name
// Opacity
=',ITOA(CUSTOM.FLAG)"
=',CUSTOM.TEXT"
Description
0 means text is a standard string, 1 means Unicode encoded string
button state number
actual length of string (this is not encoded size)
index of first character (usually 1 or same as optional index
the text from the button
button text length
Programming
91
Advertisement
Table of Contents
