Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 13 OCT 1998 09:12:53PM Tony Smisovsky wrote:

I am using a large prompt (long lines, many rows) for editing a text field (ceded as multivalue field)

I use an own written prompt editor SCRIBE.EDIT1

I want to have a gracefull way of leaving the field.

My intention is to leave the field with

Ctrl-PgDn to next prompt

and with Ctrl-PgUp to previous prompt.

I manage to write the SCRIBE.EDIT1 procedure, but it seems that the WI.NEXT does not make the trick here, as it does in "post prompt" position. So no matter if I press Ctrl-PgDn or Ctrl-PgUp, I allways leave in the same direction, that I came to the prompt.

I would apretiate an expert tip.

An improvement to this would be to

1. with the first Ctrl-PgDn go to the last line.

2. with next Ctrl-PgDn leave the prompt.

Thanks and regards

Tony.

PS. I am really gratefull, that you people from Revelation still are generous enough to support the good old AREV. It still is a great tool for many applications and the development time is still dramatically lower than any other tool known to me (and I work not only with Oracle :-)

PSS. Would it really be so bad idea, to create an ODBC bond?


At 14 OCT 1998 09:33AM Matt Sorrell wrote:

Tony,

If you are using a call to scribe, then scribe returns the ascii value of the key that was used to exit. You can test for this key, and then based on the value of that, take the appropriate action.

For instance, I have written a scribe routine to display documentation. When the user presses -

, that is flagged as an exit key. When they use this keystroke as an exit key, I know they want to print the document. I then go handle the printing in code (which allows me to control pagination), and then return to the scribe window at the same position they left it from.

If you would like, I could e-mail you a snippet of my code so you could see how I handle it.

Matt Sorrell


At 14 OCT 1998 06:05PM Tony Smisovsky wrote:

Hi Matt.

What you describe, is solved already.

I think I found some UTILITY code showing the principles of calling SCRIBE from a routine replacing the prompt editor.

What I need, is how to move to next prompt / previous prompt

based on the KEY returned from the SCRIBE routine.

Eg. the user pressed Ctrl-PgUp. He wants to walk backwards in the TEMPLATE. How can I do this?

Playing with WI.NEXT does not take me anywhere.

I think that the solution is in fiddeling with the STATUS flags.

Regards Tony.


At 15 OCT 1998 03:56AM Aaron Kaplan wrote:

Perhaps it's a setting of WC_WI% and/or a reset combination. I've done this before, so it will move to the proper place.

akaplan@sprezzatura.com

Sprezzatura, Inc.

World Leaders in all things RevSoft

www.sprezzatura.com_zz.jpg


At 15 OCT 1998 03:39PM Tony again... wrote:

Hi.

I found the solution, that probably explaines, why it was difficult to see a problem in it.

In my own routine, that called SCRIBE, I forgot to return the value (returned from SCRIBE) to the WINDOW so the prompt was left with the same key as the key that it was entered with.

After I added the line

WC=KEY

before I return from my routine,

everything is working fine.

Thank you for listening to me

Tony.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/5b23ccce451600698525669d0006ac5b.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1