
Revision 1.27, July 3, 2014
DESIGN TIME DECISIONS VS. RUNTIME DECISIONS
Another new philosophy of G5 is that not everything will be editable via NetLinx commands. Some
decisions are better made at the design time of the touch panel pages rather than at runtime in the
NetLinx code; therefore, these features should be set in TPD5 rather than in NetLinx code. If these types
of changes are needed at runtime, AMX recommends the use of multi-state buttons that are designed in
TPD5. In the long run, this can significantly simplify the NetLinx code and make maintenance and future
changes easier to incorporate.
^GDI, ^GDV, ^GRU, ^GRD, ^GDR, ^BMF…%GG, @BMF…%GG,
^BMF…%GV, @BMF…%GV, ^BMF…%GU, @BMF…%GU, ^BMF…%GD,
@BMF…%GD, ^BMF…%GR, @BMF…%GR
Bargraph Slider Name/Color
^GSN, ^GSC, ^BMF…%GN, @BMF…%GN, ^BMF…%GC, @BMF…%GC
^STF , ^BMF…%SC, @BMF…%SC
?BCB and Custom Event 1011, ^BCB , ^BMF…%CB, @BMF…%CB
?BRD and Custom Event 1014, ^BRD , ^BOR, @BOR, ^BMF…%B,
@BMF…%B
^BSO, ^BMF...%SO, @BMF…%SO
?DTO and Custom Event 1302, ^DTO
^BDO, ^BMF…%DO, @BMF…%DO
NOTE: G5 supports a modified static draw order which does NOT
support Icons, but does support multiple bitmaps and uses the
following bottom-to-top order: Fill, Bitmaps [], Text, Border. See
Appendix C for additional information.
?FON and Custom Event 1007, ^FON , @FON, ^BMF…%F,
Comentarios a estos manuales