1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 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 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Bypassing Options in ImageMode in AreaDetector |
From: | "Kasemir, Kay" <[email protected]> |
To: | Iain Marcuson <[email protected]>, "[email protected]" <[email protected]> |
Date: | Fri, 14 Sep 2018 13:58:53 +0000 |
You could layer your own mbbo record on top which then writes to the original area detector record.
In your record, note that you don't have to use ZRVL = 0 _ONVL_ = 1 TWVL = 2
You can use ZRVL = 1_ONVL_ = 2 TWVL = 16
So define the items in your mbbo to list only those values that you want to show on the UI, and create your own top-level UI with your mbbo.
-Kay
From: [email protected] <[email protected]> on behalf of Iain Marcuson <[email protected]>
Sent: Friday, September 14, 2018 9:50 AM To: [email protected] Subject: Bypassing Options in ImageMode in AreaDetector I am using areaDetector in a product. We only want to use “Single” and “Continuous” ImageMode, not “Multiple”. In the first implementation, I modified ADBase.template to remove the “Multiple” option. For a more portable solution, I made a new mbbo record without the Multiple option, and set the OUT field to $(P)$(R)ImageMode. However, I had to define “ZRVAL” and “TWVAL”, skipping “ONVAL” (Multiple), leaving a gap in a drop-down menu. Is there a way to avoid this gap?
Thank you,
Iain Marcuson Software Engineer, Sydor Technologies 585.278.1168 | www.SydorTechnologies.com Skype: [email protected]
|