I think I have found a bug in Paradox 4.0 using WAIT.  Can anyone confirm
this?

It appears that if an event-driven form of WAIT is used before a key-press
(old-style) form of WAIT, the keypress form of the WAIT command will not
correctly display the contents of its PROMPT (however its message is fine).

PROMPT commands EXTERNAL to the old form of WAIT appear to be okay.

For example:

PROMPT "THIS IS A TEST"
WAIT WORKSPACE
   PROC "MyWaitProc"
   KEY "F2"
ENDWAIT

At this point, the prompt should be automatically cleared by PAL...

WAIT WORKSPACE
   PROMPT "YOU DO NOT SEE ME"
   MESSAGE "YOU DO SEE ME"
UNTIL "F2"

When the 2nd WAIT is executed, the FIRST prompt ("THIS IS A TEST") will
be the prompt on screen.  One solution is to move the PROPMT out of the
WAIT ... UNTIL, but this requires an empty PROMPT after the WAIT to clear
the prompt line.

So, has anyone else seen this, or am I making a silly mistake?  Of course,
there is no problem is one ALWAYS uses event driven WAIT's...

    -Todd

Hugs and backrubs -- I break Rule 6

{*filter*} vanilla {*filter*} het

You should issue a PROMPT command without any parameters between two Waits
in order to give up control of PROMPT and Paradox regain control of it. I
am copying your example below with the fix.

PROMPT "THIS IS A TEST"
WAIT WORKSPACE
   PROC "MyWaitProc"
   KEY "F2"
ENDWAIT

PROMPT

WAIT WORKSPACE
   PROMPT "YOU DO NOT SEE ME"
   MESSAGE "YOU DO SEE ME"
UNTIL "F2"

It works fine.

hope it helped...
--nasir