EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: EPICS UIs in the context of changing enum record identifiers
From: Jameson Graef Rollins <[email protected]>
To: Andrew Johnson <[email protected]>, Mark Rivers <[email protected]>, EPICS tech-talk <[email protected]>
Date: Wed, 01 Apr 2015 12:04:56 -0700
On Wed, Apr 01 2015, Andrew Johnson <[email protected]> wrote:
> On 04/01/2015 01:24 PM, Jameson Graef Rollins wrote:
>> Unfortunately I haven't yet figured out to get MEDM to monitor the
>> DBE_PROPERTY.  If anyone knows how to do that, I would love a
>> reference.
>
> Ken Evans was the last real maintainer of MEDM and I think he retired
> before we added the DBE_PROPERTY event type to Base, so I don't think
> you're going to get any responses to that question.
>
> I have an alternative suggestion which may or may not work for your
> issue depending on how dynamic your enum strings are: Replace the Menu
> Button pointing to your enum with a Text Update widget (to display the
> current setting) and a series of Message Buttons, one for each
> possible value, each of which will put their specific command string
> to the enum record on pressing the button.
>
> By putting a string value you don't care if the numbers for the enum
> commands change. You will also want to arrange for the buttons for
> those commands not currently enabled to be disabled (made invisible),
> which will probably need additional PVs to work. This does couple your
> MEDM screens more closely with your application, but that might not be
> too much of a problem.

Hi, Andrew.  This is an interesting suggestion, and is similar to what
Pete described.  The drop down menu interface is actually quite nice in
our case, though, and ultimately the point is that we were hoping to
able to continue to use something like it.  Individual message buttons
for all options makes the interface much bulkier and more unwieldy.

I guess I should have mentioned, since similar things have been
suggested, that we also have a sub-screen that is generated on the fly
with individual message buttons for each selection option.  It doesn't
get updated when the options change, but it at least eliminates the
problem of selecting the wrong element unknowingly.

jamie.

Attachment: signature.asc
Description: PGP signature


References:
EPICS UIs in the context of changing enum record identifiers Jameson Graef Rollins
RE: EPICS UIs in the context of changing enum record identifiers Mark Rivers
RE: EPICS UIs in the context of changing enum record identifiers Jameson Graef Rollins
Re: EPICS UIs in the context of changing enum record identifiers Andrew Johnson

Navigate by Date:
Prev: Re: EPICS UIs in the context of changing enum record identifiers Andrew Johnson
Next: RE: STAT=SCAN recover Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: EPICS UIs in the context of changing enum record identifiers Andrew Johnson
Next: Re: EPICS UIs in the context of changing enum record identifiers Pete Jemian
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·