Programming
57
Modero G4 Touch Panels - Configuration & Programming Manual
Button Commands
These Button Commands are used in NetLinx Studio and are case insensitive. All commands that begin with “^” have the capability
of assigning a variable text address range and button state range.
A device must first be defined in the NetLinx programming
language with values for the Device: Port: System
(in all programming examples -
Panel
is used in place of these values).
Variable text ranges
allow you to target 1 or more variable text channels in a single command.
Button State ranges
allow you to target 1 or more states of a variable text button with a single command.
“.”
Character is used for the 'through' notation, also the “
&
” character is used for the 'And' notation.
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 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 7 fields:
These fields are populated differently for each query command. The text length (String Encode) field is not used in any command.
Page Commands (Cont.)
PPON
Activate a specific popup page to launch on either a specified page or the current page.If the page name is empty, the current
page is used (see example 2). If the popup page is already On, do not re-draw it. This command works in the same way as the
’Show Popup’ command in TPDesign4.
•
Syntax
:
"'PPON-<popup page name>;<page name>'"
•
Variables
:
popup page name = 1 - 50 ASCII characters. Name of the popup page.
page name = 1 - 50 ASCII characters. Name of the page the popup is displayed On.
•
Example 1
:
SEND_COMMAND Panel,"'PPON-Popup1; Main'"
Activates the popup page ’Popup1’ on the Main page.
•
Example 2
:
SEND_COMMAND Panel,"'PPON-Popup1'"
Activates the popup page ’Popup1’ on the current page.
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
