| 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 |
I don't suppose there is a way to specify that forms other than
OAN$LIST/OAN$READ$MORE/OAN$READ$MENU are to be used with the NOTES LIST
function? For example, some undocumented mechanism analogous to the
LIST function's /OVERLAY and /MORE qualifiers.
We have an application based on GPC, and its Read option only gives
users a limited menu and does not display the header block. We cannot
simply customize OAN$LIST etc because the standard GPC subsystem must
coexist and be unaffected by our application.
Under ALL-IN-1 V2.4 we had our own forms based on OAN$READ and
OAN$READ$MENU. If it is not possible to specify forms to NOTES LIST,
we will probably keep using the old method. Is it safe to continue
using the undocumented scrolling DSAB OAN$TEXT?
Thanks in anticipation (to Tony, no doubt!)
Fiona.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2029.1 | Try using NOTES READ | IDNTCR::RHOTON | John Rhoton @TNO - DTN 871.7947 | Mon Jan 04 1993 09:28 | 28 |
Re: .0
> I don't suppose there is a way to specify that forms other than
> OAN$LIST/OAN$READ$MORE/OAN$READ$MENU are to be used with the NOTES LIST
> function? For example, some undocumented mechanism analogous to the
> LIST function's /OVERLAY and /MORE qualifiers.
When you issue a NOTES LIST note-id it is translated to
FORM OAN$LIST LIST /CAPTIVE/PRE_FUN="FORCE"
/HARD=OA$_OA_LIST_HRD_LIST_FILE <NOTES READ note-id
/OVERLAY="OAN$READ,ON" /DATA=1
NOTES SET_SEEN note-id
I would think you could accomplish what you want by making a similar call
but a different form although I have not tried this out. NOTES READ is
the actual pipeline function that does all of the work. NOTES LIST is just
an easier interface (if you want to use OAN$LIST).
> Under ALL-IN-1 V2.4 we had our own forms based on OAN$READ and
> OAN$READ$MENU. If it is not possible to specify forms to NOTES LIST,
> we will probably keep using the old method. Is it safe to continue
> using the undocumented scrolling DSAB OAN$TEXT?
OAN$TEXT should still work safely.
John
| |||||
| 2029.2 | DUBSWS::REDMOND | Tony Redmond | Mon Jan 04 1993 10:24 | 7 | |
John's answer gives you the background to a potential solution.
However, be careful if you do keep old GPC forms in use. A lot of bugs
were fixed in V3.0 and the fixes should really be brought into your
versions of the old forms. In particular I should check out the code
that deals with moderator, keyword, and write regardless privileges.
Tony
| |||||