FEED_WKEYBOARD@ usage and limitations

I've been using FEED_WKEYBOARD@ successfully to feed in a <CR> into the keyboard buffer so my using program could take internal action on it.

Because the <CR> is sucked up by the ClearWin+ functions, the ENTER trap is useful to detect the usage, then take action. I use the key trap [winio@('%ac[Enter]&',enter_key)] to trap the usage, then feed the carriage return back [CALL FEED_WKEYBOARD@(13,ICODE)] for the using program to interpret it. Works great!

I now have a function called from the active ClearWin+ window, but the FEED_WKEYBOARD@ call has no apparent effect. I have also tried a couple of other keycodes that perform specific functions when detected, and they do not appear to be sensed as well. Indeed, it appears to confuse the key press message processing, causing the program to be unable to interpret any key press information.

I was wondering if the use of this function has restrictions, such as only being used when the current message being processed in ClearWin+ is key press message?

The main limitation with FEED_WKEYBOARD@ is that it can only be used with a ClearWin window. This is NOT the same as a ClearWin+ window.

ClearWin predates ClearWin+ and in ClearWin+ it is represented by %cw.

Thanks, Paul.

This may help me 'fix' the issue, or just move onward!!

Might ADD_KEYBOARD_MONITOR@ be of some help?