In addition to the additional programming required (multiple XCALL XTEXT operations using different opcode values), these present the problem of how to respond to the user clicking on the edit control when some other input field has the input focus (i.e. when not inside of an XCALL XTEXT operation). You can prevent this problem by disabling the control on exit (see flags TXF_DISABLE) or you can define a keyboard click-to-enable string in TXC.KBDSTR, which would be received by whatever input routine had the focus at the time the user clicked on the text control. This would allow your application logic to take appropriate action, presumably including executing a new XCALL XTEXT operation. If you neither disable the text control when inactive, nor define a click-to-enable string in TXC.KBDSTR, then the user may have the impression of operating on the control, but your program will not be aware of it. (That might be acceptable though, since the application could retrieve the current text at a later time by executing XCALL XTEXT with opcode set to TXOP_SAVE.)
The recommended format for TXC.KBDSTR, is "VK_xF###" where ### is the absolute value of the desired negative exitcode value to be returned when the user clicks on the text control while another input control has the focus (i.e. INFLD, XTREE, AUI_EVENTWAIT, etc.) For example, "VK_xF901" would generate exitcode -901.
