I have been searching the knowledge base

and here is another little thing I have not been able to make work. In many window's forms (even the url locator prompt in my browser) if you start to type over (edit) the information in a prompt and decide to quit and return to what was there all you have to do is hit the escape key.

Any easy way to do that in OI controls

Ed,

Assuming that you won't need ESC for anything else you can create an invisible menu item that calls a QuickEvent that does the following:

QuickEvent Options: Execute a procedure

Entity: SYSPROG*STPROCEXE**SEND_MESSAGE

Parameters: '@FOCUS','UNDO'

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Thanks so much. That has actually filled in a bit of information I was missing. Slowly I am learning this stuff!

Ed,

Don: Assuming that you won't need ESC for anything else …

What springs to mind is the custom of using Esc to close (cancel) dialogs, i.e, as the equivalent of pressing the Cancel button in dialogs.

- Oystein -

You are correct about that. There is a bit of a conflict there. Again in AREV escape could be used repeatedly to move you back one level of operations and cancelling the whatever you were doing at the time. I do not know how many times I have told clients - you get in trouble just keep hitting the escape key. I will haveto make a decision on which way I want to handle the escape key.

One of the issues my DOS clients face when moving to Windows is that the user-interface is different .. and consequently can get them into trouble. I've retained many of the DOS keyboard items (F9, F8, F2, F1, etc.), but I've opted not to enable the Esc key the same way. There are too many controls that use it (and many of these are called from within the context of a window). I can use the Esc key in MSG dialogs to get people out or to provide a way to back up to a previous dialog, but you have to spend a little bit more time implementing it. In AREV you didn't have to do nearly as much and since the movement of the cursor was strictly under program control you didn't have to try to figure out where the user came from or whether they had completed the entry there. Windows does not easily offer this capability without a great deal of work.

I'd be leery of pre-empting the Esc key in a hidden menu item, in general, FWIW.

Don M.

Thanks for your insights. I somtimes wonder if we are actually making steps forward not . At nights after a frustrating program session I sometimes wonder

ed

View this thread on the forum...