> Hello Fritz:
>
> I completely agree with your idea but wonder about the implementation.
>
> menu(aoDRLM) {
> choice(aoDRLM_Clamp,"Clamp")
> choice(aoDRLM_Reject,"Reject")
> }
> works for setting bit 0 to Clamp/Reject.
>
> But how would you define the menu so that other bits
> are included?
> Assume bit 1 would define the "X" behavior, this works:
>
> menu(aoDRLM) {
> choice(aoDRLM_Clamp,"Clamp, No X")
> choice(aoDRLM_Reject,"Reject, No X")
> choice(aoDRLM_X_Clamp,"Clamp, Use X")
> choice(aoDRLM_X_Reject,"Reject, Use X")
> }
>
> But using menus for fields where each bit has a meaning
> soon becomes awkwards.
>
> -Kay
Kay,
Well, this is where the concept has a few rough edges. To use a
menu to assign the possible values it would be necessary to have an
identifier string for every possible combination of bits. For more
than a few bits, this is prohibitive. In the cases where I have used
a mode field, I have made it an integer or short integer and assigned
a hexadecimal value in the record instantiation.
Fritz
- Replies:
- Re: AO Record: New Drive Limit Mode? Bernd Schoeneburg
- Navigate by Date:
- Prev:
Re: AO Record: New Drive Limit Mode? Bob Dalesio
- Next:
RE: NAN and INF Rarback, Harvey
- 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
- Navigate by Thread:
- Prev:
Re: AO Record: New Drive Limit Mode? Jim Thomas
- Next:
Re: AO Record: New Drive Limit Mode? Bernd Schoeneburg
- 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
|