| 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: Medm Menu Object with non-sequential choices |
| From: | Mark Rivers <[email protected]> |
| To: | "'Newby, Mary A'" <[email protected]>, "[email protected]" <[email protected]> |
| Date: | Mon, 20 Feb 2017 19:39:48 +0000 |
|
Hi Mary, I think you may be confusing the enum index with the enum value in an mbbo record, for example. Are you skipping enum indices because you think the enum values need to
match the enum index? They do not. Here is an example: record(mbbo, "$(P)$(R)TriggerMode") { field(ZRST, "Internal") field(ZRVL, "0") field(ONST, "External") field(ONVL, "1") field(TWST, "External Start") field(TWVL, "6") field(THST, "External Exposure") field(THVL, "7") field(FRST, "External FVP") field(FRVL, "9") field(FVST, "Software") field(FVVL, "10") } Note that the indices are consecutive (ZR-FV) but the values are not. This will display nicely in medm with no missing lines, but the correct value will be sent to the
driver. Mark From: [email protected] [mailto:[email protected]]
On Behalf Of Newby, Mary A I am a new user to MEDM, and I am wondering if it possible to tie a non-sequential list of enumeration values to a menu object? I have attempted to do this, however, for the enumeration values that are not in the record, the menu displays
a blank line for this values and we don’t want the blank lines.
Mary Newby |
