> Francois replied: > > I think TTnScript is the way to go. You can dynamically add/remove events > according to which "screen" you detect. If you don't use TTnScript, has a > look at his source code to understand how to get hand on the input stream to > chack for data. > > I also uploaded a modified version of the components. It is a proposal of > changes by John Porteous. It will probably appear shortly in the > distribution. You may try it: > http://www.overbyte.be/arch/dump/EmulVTJohnPorteous.zip > >
Hello, I already looked at TnScript 2-3 minutes, but I think this only works if the Telnet session is designed like this: Step 1 - Step 2 - Step 3... so each step is a screen completely different from each other. My session will more look like this: Step 1 (Screen 1) - Step 2 (Screen 2) - Step 3 (Screen 1 again) etc. so the same screen will come again and again. Do you have a short example of this (for my special case)? And I can't guarantee that the last line is always the same for these screens, because the vendor of the device to be configured could enhance the configuration... Or some explanaitions on OnDataAvailable, OnLocalEcho, the properties LocalEcho and Backlog? And in my app. I see that the telnet session is messed up, means part of the screen which should be displayed top is "delayed" and thus displayed at the bottom rather. I think it comes from sending the next command to fast (when not yet all data has been received from the old one) so it messes up. One idea of mine is to send the first command, wait for the first OnDataAvailable and then do a sort of busy wait or similar until a certain period is over so that delayed OnDataAvailables for the same screen can pass and then send the next command. Is this feasible? Otherwise I'd use a TnCNX if the TnScript based method doesn't work. Greetings Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
