Multiple UI modules or TP Arrays?
John Gonzales
Posts: 609
I like to define multiple UI module instances to handle multiple touchpanels. Do others tend to instantiate multiple UI modules or do you prefer to use a single UI module and handle all of the TP's in one module using a TP array?
I'm wondering if there's a disadvantage to multiple UI module instances. To give an example: to handle an array of 100 light switches from 20 panels, do you just set up a TP array with all 20 panels, then track panels and pages and send commands to the comm module based on who's pushing what, or do you set your UI module up to handle a single TP, pass each TP's device number to it's own module then let each UI module send commands to the comm modules from there?
I find that there is a lot less tracking for page flips, panels, variable text addresses, etc..., and it's easier to deal with multiple users controlling the same device group at the same time when you use multiple UI instances.
--John
I'm wondering if there's a disadvantage to multiple UI module instances. To give an example: to handle an array of 100 light switches from 20 panels, do you just set up a TP array with all 20 panels, then track panels and pages and send commands to the comm module based on who's pushing what, or do you set your UI module up to handle a single TP, pass each TP's device number to it's own module then let each UI module send commands to the comm modules from there?
I find that there is a lot less tracking for page flips, panels, variable text addresses, etc..., and it's easier to deal with multiple users controlling the same device group at the same time when you use multiple UI instances.
--John
Failed to load the poll.
Failed to load the poll.
0