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: Mark Rivers <[email protected]>
To: "'Jameson Graef Rollins'" <[email protected]>, EPICS tech-talk <[email protected]>
Date: Wed, 1 Apr 2015 17:01:48 +0000
One ugly solution that I have used is to only display those widgets on little screens that are meant to be opened temporarily and then closed.  Each time the screen is opened it will get the latest values of the enums.

The problem is not the client applications so much as it is a limitation on Channel Access monitor types.  See the recent tech-talk thread about DBE_PROPERTY subscriptions.

Mark


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Jameson Graef Rollins
Sent: Wednesday, April 01, 2015 11:54 AM
To: EPICS tech-talk
Subject: EPICS UIs in the context of changing enum record identifiers

Hi, all.  We have an application that employs an enum record as a
control interface (for submitting a request to the program).  The
application can be manually prompted to reload it's configuration, which
can occasionally cause the elements of the control enum to change
(desired behavior).

The problem is that our operator interfaces (primarily MEDM at the
moment) do not behave well in the context of these enum change.  All
MEDM enum controller objects retrieve enum identifiers only once at
startup.  This means they become stale after the enum changes, and more
dangerously, allow the user to select one element that is actually
mapped to another.  This has created quite a few headaches for us.

I've been trying to find a way around this problem, but haven't come up
with anything.  The best solution I have so far involves creating a
screen on the fly that creates a shell command menu with a bunch of
"caput" commands for the strings of enum.  This of course doesn't get
updated on application reload either, but it at least doesn't allow for
selecting a mislabeled element.

I'm soliciting for suggestions about how to create operator interfaces
that behave better in the face of changing enum records.  All operator
interfaces that I've looked at (MEDM, EDM, QTDM) don't behave well.  Any
suggestions of what we could do that don't involve patching MEDM or
creating our own operator interface?

jamie.


Replies:
RE: EPICS UIs in the context of changing enum record identifiers Jameson Graef Rollins
References:
EPICS UIs in the context of changing enum record identifiers Jameson Graef Rollins

Navigate by Date:
Prev: EPICS UIs in the context of changing enum record identifiers Jameson Graef Rollins
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 
Navigate by Thread:
Prev: EPICS UIs in the context of changing enum record identifiers Jameson Graef Rollins
Next: RE: EPICS UIs in the context of changing enum record identifiers Jameson Graef Rollins
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 ·