It doesn't appear that anyone better qualified than I has jumped in and tried to help you, so I guess I will. > Before spending a bunch more time on something that may be totally wrong I > felt I should ask where the right location for this inserting of GUI data > is, tn5250_session_save_screen() or (most likely) > tn5250_wtd_context_convert_nosrc()? I would think that you'd want to add a routine called tn5250_wtd_context_write_wdsf() or something similar that reinserts any GUI data that was passed (not just the window orders) to the wtd. Then, yes, you'd probably want to call it from tn5250_wtd_context_convert_nosrc() > If the latter, how do I know what the current buffer address is so that > I can insert the window information correctly? Would it work to append > a WTD order to the end of the existing WTD order and put into the > appended order just the GUI data? I would expect that you'd add the new data to the end using tn5250_wtd_context_putc() -- but if it doesn't belong at the end (perhaps it belongs before the wtd command, I don't know -- you'd have to look at how the data gets received originally from the '400) then you could put it earlier in the stream just by changing where the code is called in tn5250_wtd_context_convert_nosrc()
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.