Re: [Cs-studio-users] Status and alarm handler severity in a BOY widget

[Kasemir, K. <kas...@or...>]

Hi:

I would avoid rules & linking containers.
Use a suitable widget, set the PV name, done.
Maybe adjust some properties beyond the PV name.
But don't use polylines with visibility rules, linking containers with rules and so on to create a widget that doesn't exist.
If you want a widget that doesn't exist, create that widget.
What you want to do in your first bullet is similar to the symbol widget that ITER created.
Maybe coordinate with them if additional properties of the symbol widget could allow what you want to do?

For the alarm acknowledgement, contact Eric about his PVManager additions to support alarms. Basically, he worked on displaying the alarm state from the alarm server in a PV, and allowed acknoledgement from writing to a PV.

For the menu-button-as-combo box, that might also be something that you'd have to do.
If you want the menu button to have such an option, then please consider implementing that as an option on the menu button widget.
A caveat might be that we already have some issues with the mix of native (SWT) and drawn (Draw2d) widgets. Originally, all widgets were drawn by BOY, and thus all "worked": Widgets in containers are correctly cropped when (partially) hidden, the layering is OK. With SWT-based widgets, you do get support for ' Tabbing' from widget to widget, they have the native look, but some tricks were necessary to make them fully work. Since Xihui is no longer working on this, check those widgets that use SWT controls carefully to learn about these details when you implement a combo box option for the menu button.

Thanks,
Kay


* The top line symbols are a red and a green stacked BOY Polyline drawings with visibility rules and an action to open an OPI on click. Should I turn them into PNGs and use a multistate symbol widget? Or just put the two drawings into an OPI screen complete with rules and use a linking container?

* The middle line symbols are linking containers with action to open an OPI on click. The linking container OPI file contains an image, a label, and a rounded rectangle with rules for colour and alpha. This is really a button, so should I extend the button widget with a new display type? I would also like to use these buttons in sub-screens, so it would be good to avoid having to distribute this linking container OPI with all sub-screens.

* The component state and severity come from chained calc records in an IOC. I would like to be able to acknowledge alarms from this screen, so I wonder if there is any merit in using the alarm system. Has anyone else done anything similar?

* The "Open" buttons are Menu buttons. I was expecting a way to be able to style them as combo boxes, but this seems to not be available. Is there some other way to get a native combo box with entries from an mbbo in BOY?

Thanks,
Tom Cobb





--

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.

Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.

Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.

Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom