Adam, Be aware though, that if you ever ungroup the object, any actions assigned to the group will disappear without a trace! Regards =20 Terry=20 Terry Lloyd, Systems Engineer ____________________________________________________________ * Building W601, Mail BA111C * Voice: +44 (0)1446 723501 Dow Corning Ltd * Fax: +44 (0)1446 700874 Cardiff Road * E-Mail: terry.lloyd@xxxxxxxxxxxxxx Barry Vale of Glamorgan, CF63 2YL ____________________________________________________________________ -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Adam.Pemberton@xxxxxxxxxxxx Sent: Tuesday, January 23, 2007 4:01 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] FoxView momentary contact and close problem - solution Just a little titbit we have recently learnt that might be useful for the list. =20 In our conversion from Display Manager to FoxView we have noticed that some buttons on overlays stopped functioning correctly. This turned out to be because of a subtle feature in Display Manager that appears not to be supported in Foxview. =20 As most will be aware, one can only assign 1 action to any graphic element. This is not usually a problem as one can use the DM Command action to perform a number of dmcmd commands. Unfortunately there is no dmcmd command for the Momentary Contact action. =20 Our problem was that, in Display Manager, we configured most of our buttons on overlays to have "DM Command" actions such that when the button is pressed two things happen: the command is executed and the overlay is closed.=20 For the case of a momentary contact action, we got around the 1-action limitation by configuring the button with two rectangles, each with its own action. One of the rectangles was assigned the Momentary Contact action and was given a name (Ack say). The other rectangle was assigned a DM command and performed two actions: dmcmd pick Ack dmcmd close Now the crux: this does not work in FoxView. =20 Our initial solution was to provide an extra "OK" button to close the overlay. However a colleague came up with a better solution. Given the various elements of the button are grouped, our solution was to assign the momentary contact to the Group (rather than a rectangle) and assign the close command to the rectangle. For some reason, when it's assigned in a vertical hierarchy it seemed to work. =20 Hope this helps someone, or leads to a better solution from someone else. =20 Regards Adam Pemberton Site Electrical & Control Systems Engineer Lihir Gold Limited Ph: +675 9865 655 Fax: +675 9865 666 Mob: Nogat Postal: Australia: GPO Box 905, Brisbane, QLD 4001 PNG: PO Box 789, Port Moresby, NCD =20 =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave