RE: making edm draw the desired related display based on value of a PV

[<tom.cobb@diamond.ac.uk>]

Hi,

If I've understood this correctly, there are 2 ways you can do this:

1) Use (560) menu muxes on the top level screen. Point each menu mux to
the PV that provides $(MODE) as an integer value, and get it to populate
a macro that is used to launch the correct related display for that
trigger

2) Make a pdu_trig_generic.edl display with contains only an embedded
window, and get all the related displays to launch this. Make this
embedded window use a menu source, and point the PV to an mbbo that has
$(MODE) as its value for that trigger. You can then fill in the 4
entries in the embedded window with edm screens for your 4 modes

Personally I'd choose option 2.

Thanks,
Tom Cobb,
Diamond Light Source Ltd.
Diamond House
Harwell Science and Innovation Campus
Didcot
Oxfordshire
OX11 0DE
Tel +44 (0) 1235 778582
 

> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov 
> [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Dayle Kotturi
> Sent: 02 November 2010 22:56
> To: tech-talk@aps.anl.gov
> Subject: making edm draw the desired related display based on 
> value of a PV
> 
> Hello,
> 
> In our timing system, there are four possible modes of 
> triggers.  I want
> to display all 560 triggers the same way, putting their names 
> as the label
> on related display widget buttons, regardless of the mode of 
> the trigger.
> 
> When the user clicks on the trigger name, a generic related 
> display is 
> passed the trigger name and mode as macros. The generic display
> contains an embedded window widget which draws the appropriate "form",
> in "Display Source", by mangling the name of the 
> mode-appropriate display
> name for "Display File Name" via pdu_trig_$(MODE).edl into one of the 
> four possible filenames.
> 
> This is all ok, but it means I have to have to hardcode the 
> definition of
> $(MODE) into the macros for each trigger.
> 
> Is there a way that I can display the correct edl file based 
> on the value
> of a PV of the MODE at runtime? The modes are not going to be 
> changing between
> boots.
> 
> I had envisioned drawing all four related displays and then 
> using visibility
> rules, but related display widget does not have visibility 
> rule option. I don'tknow if they can be "grouped" to widgets 
> that do have this option.
> 
> thanks for any help,
> 
> Dayle Kotturi                                       
> dayle@slac.stanford.edu
> Controls Department 
> SLAC National Accelerator Laboratory
> 

-- 
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