>>>>> "Kay" == Kay-Uwe Kasemir <[email protected]> writes:
Kay> As Andrew indicated, the optimal solution would be on the GUI side:
Kay> Enter a wrong value, it's rejected.
Stop right here. It's rejected with a message.
Kay> Enter it again, a message box displays "XXX is not within DRVL
Kay> ... DRVH". Enter it again, a voice says "XXX is still not within
Kay> DRVL ... DRVH" etc. There should be a configurable list of actions.
Kay> While we are updating edd/dm, medm, dm2k, edm and all the custom CA GUIs
Kay> written in tcl, python, Visual Basic, ...
Kay> DRLM="Reject" sounds like the best near-term solution to me.
To provide another voice on Andrew's side, tough, they're all broken. The
AO record already protects itself against garbage input. IMHO the GUI
should not be inserting junk into the system. That's an input editing
function, for which the GUI already has the necessary information.
I'll be quiet now ;-) That's a particular sore spot for me anyway.
Jim
- References:
- RE: AO Record: New Drive Limit Mode? Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
RE: AO Record: New Drive Limit Mode? Kay-Uwe Kasemir
- Next:
Re: AO Record: New Drive Limit Mode? Andrew Johnson
- 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? Kay-Uwe Kasemir
- Next:
Re: AO Record: New Drive Limit Mode? J. Frederick Bartlett ([email protected])
- 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
|