Hiya,
I've recently been investigating the functions and objects available in Attachmate Extra! and was unable to find any information on the following subject.
I want to know the repercussions of changing our WaitHostQuiet calls to checking the status of the XClock instead.
My understanding of the WaitHostQuiet call is that it will wait for a specific amount of time until after the last receipt of data from the host and then return.
I'm hoping to speed thing up by checking the status of the XClock and returning when it is no longer present - ie that all the data on the screen has been updated.
Has anyone done this previously or know of any reason why it should/shouldn't work? Any information would be greatly appreciated.
Thanks,
Mayhem79.
I've recently been investigating the functions and objects available in Attachmate Extra! and was unable to find any information on the following subject.
I want to know the repercussions of changing our WaitHostQuiet calls to checking the status of the XClock instead.
My understanding of the WaitHostQuiet call is that it will wait for a specific amount of time until after the last receipt of data from the host and then return.
I'm hoping to speed thing up by checking the status of the XClock and returning when it is no longer present - ie that all the data on the screen has been updated.
Has anyone done this previously or know of any reason why it should/shouldn't work? Any information would be greatly appreciated.
Thanks,
Mayhem79.