[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
405.0. "Wish: OA$FLD_SKIP function, and /SKIP field qualifier" by HOTAIR::MADDOX (DIGITAL Alien) Thu Apr 02 1992 21:49
I would like to see an OA$FLD_SKIP function. This purpose of this function
would be to set the field disposition to SKIP, i.e., don't allow the user
on this field. The field would be ignored as if it were not included in the
/FIELDS= list, but this function would need to be issued each time the user
attempted to move to that field.
A corresponding field qualifier might be /SKIP with the form /SKIP='test
function\\OA$FLD_SKIP'. This qualifier might not be necessary if the
OA$FLD_SKIP function could be used reliably in the /PRE qualifier.
The advantage of the OA$FLD_SKIP as opposed to OA$FLD_NEXT and related
functions is that the programmer would not need to test OA$FIELD_TERM_NAME to
determine where to land instead of this field. I.e., if the user pressed
TAB, DOWN, GOLD T, or NEXT SCREEN the cursor would advance. If he pressed
BS, GOLD B, or PREV SCREEN the cursor would back up one field. If he
pressed UP the cursor would advance if there were another field on that line
and back up if not.
You can see that an OA$FLD_SKIP would save the application developer from
having to think about and code in lots of tests.
Thanks,
Joe
T.R | Title | User | Personal Name | Date | Lines |
---|
405.1 | Yet another vote | UTRTSC::BOSMAN | We're just sugar mice in the rain | Fri Apr 03 1992 08:28 | 3 |
| Here's another vote for OA$FLD_SKIP.
Sjaak.
|