Up-arrow problem resolved.

[Deskin, Bob]

If we told you all the secrets then I couldn't expose them and look
brilliant. Seriously though, we do try and document everything, but we're
only human. Especially when things go in between major releases, get
documented in release notes, and then get forgotten. I honestly don't know
where ENTRYRECALL is documented except the Handbook. It was created to bring
back behavior on OpenVMS PowerHouse that was lost because of how PowerHouse
Client had to work. With PowerHouse Client, any data in the buffers is
assumed to be dispalyable when the form appears. What this would mean is
that all that data in the recall buffers would be predisplayed for the next
record to be entered. This is not what you usually want since the user could
just transmit and get a duplicate record. But this is default windows
behavior. Keep in mind that on a terminal we don't automatically predisplay
the buffers, you need either PREDISPLAY or the recall (up-arrow). So to have
the windows-like functionality, we had to clear the buffers between records.
After all, there is no recall in PowerHouse Client. To add the functionality
back in, we added the ENTRYRECALL parameter for terminal users. And by the
way, this behavior (on entry) sort of snuck in as well. It wasn't there for
the original recall in 6.00. And was never on UNIX or MPE/iX until the later
7.xx versions (I think).

Bob Deskin              
Senior Product Advisor  bob.deskin@cognos.com
Cognos Inc.             (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


> ----------
> From: 	pickerij@norbord.com[SMTP:pickerij@norbord.com]
> Sent: 	December 15, 1998 4:07 PM
> To: 	Allison.Hamilton@cognos.com; powerh-l@lists.swau.edu
> Subject: 	RE: Up-arrow problem resolved.
> 
> Allison says ...
> 
> >I think that entryrecall is VMS specific, at least in older versions.   
>  It
> >was implemented to return VMS functionality after the cross-platform
> >implementation that I previously mentioned.  (I forgot Entryrecall... )
> 
>    
> 
> 
> Entryrecall seems to work in version 8.19.c3 which is definitely NOT a   
> Compaq version. That is, it acts like ctrl-b in change and correct modes
> 
> but as duplicate in entry mode. Pretty neat actually :-)
> 
> Is it here to stay? Or is it a fleeting parameter that might go away in   
> the next release?
> 
> And you didn't answer either question in my original post :-(
> 
> Where are these things documented and what other secrets are there? I   
> hate reverse engineering Quick behaviour :-0
> 
> JWP
> 
> > ----------
> > From:  pickerij@norbord.com[SMTP:pickerij@norbord.com]
> > Sent:  Tuesday, December 15, 1998 3:42 PM
> > To:  powerh-l@lists.swau.edu
> > Subject:  RE: Up-arrow problem resolved.
> >
> > >And the winner is...ENTRYRECALL.
> > >
> > >The ERRORRECALL ...  ??
> >
> > Cool :-) Now just where are these secrets documented?????
> >
> > Entryrecall works as discussed in previous posts (errorrecall doesn't)
> 
>     
> 
> > but it isn't mentioned anywhere in either the paper 7.29 manual or the
> 
>     
> 
> > new CD 8.19 manual.
> >
> > What other secrets are there??
> >
> > John Pickering
> > JWP Systems Inc
> > Toronto
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> Subscribe: "subscribe powerh-l" in message body to
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a subscriber.
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.