type ahead characters disappear until later when reopen floating window

[RobertRedekop]

Hi everyone.

I've got an odd problem, but it's intermittent.  I made a bunch of changes a while back, one of which was adding "bind to thread" to all my windows (they should all be bound to the same thread).  Before that, this problem did not happen.

Situation.  Have one floating window.  Start a 2nd floating window.  Type info into that 2nd window.  Hit the key which triggers the program to close that window.   I keep typing, wanting to fill in the fields in that first window that I just told the program to make active again.  Sometimes, the first few keys I type "disappear" only to show up later when I create another floating window.

Anyone know what this is?

Is it related to "bind to thread"?

Any idea how to handle this?

(I've tried adding a little "buffering" routine to read all characters that are available according to "ACCEPT FROM INPUT STATUS" and save them in a buffer before closing the window.  No change in behavior, the characters still get saved for later)

[shjerpe]

Are you using the SET phrase to designate which window is Active? Here is a forum response that may help.

https://community.microfocus.com/t5/Extend-and-AcuCOBOL-Forum/threads/m-p/1732130#M11311

[RobertRedekop]

While I use "SET I-O" in a couple places, I do not do so when closing the window, so at that point the active window would have been undefined.  I've added a SET I-O to the close function, to set that property for the next "lower" window.  Now have to wait and see if problem continues.

[RobertRedekop]

Still happens.