I am writing a screen-scraping app using some third-party VT/Telnet classes, which aims to drive a unix green-screen app as if the user were typing directly into it.
I react to gotFocus events on my windows form controls, which triggers data to be sent to unix, possibly in several bursts. I react to the multiple endReceive events that get fired when Unix talks back.
I need to keep the unix app and windows form in step, and this would seem to be easier to acheive if i can disable user interaction on the windows form until my app assumes that unix has got where it was directed to go i.e. no more endReceives are forthcoming and I can identify where the cursor is on screen.
What approaches would achieve this aim?
I could set enable=false on the form, which results in the usual grey, flat look. However, assuming the two sides of my app get in step relatively quickly this would result in the screen 'flickering' unacceptably between colourful and grey on a very frequent basis.
I react to gotFocus events on my windows form controls, which triggers data to be sent to unix, possibly in several bursts. I react to the multiple endReceive events that get fired when Unix talks back.
I need to keep the unix app and windows form in step, and this would seem to be easier to acheive if i can disable user interaction on the windows form until my app assumes that unix has got where it was directed to go i.e. no more endReceives are forthcoming and I can identify where the cursor is on screen.
What approaches would achieve this aim?
I could set enable=false on the form, which results in the usual grey, flat look. However, assuming the two sides of my app get in step relatively quickly this would result in the screen 'flickering' unacceptably between colourful and grey on a very frequent basis.