Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Program flow and exit and rxdata

Status
Not open for further replies.

flea333

Technical User
Sep 4, 2003
47
US
When a proc uses 'call' to run another proc, then that proc calls another proc, do the procs return to their calling procs in the order in which they were called?

Also when 'exit' is executed, the script completely stops right?

I have aspect display off so that the user doesn't see the transmit commands. Then I try to turn the display on again so the user can see those commands, however those commands dont end up being displayed until I use the command termmsg. Then what happens is the termmsg string is printed, then the rx buffer is spit out. Why?
 
The answer to your first two questions is yet.

I did not see the problem with set aspect display on that you are when I ran a quick test. Does your script also modify set aspect rxdata? If so, there could be some data remaining in the receive buffer that is triggered by the termmsg command. If so, you could use the rxflush command to clear out any received data that has not been processed by your script.


aspect@aspectscripting.com
 
My script does turn on rxdata so and turns off the display so that I can wait for something without the user seeing it. Then I want to turn on the display, which I do, but it still doesn't print out the stuff on the buffer until I use the termmsg command. Is there some command I'm missing to get the display back on?
 
Whats happening exactly is that I have rxdata on and display off, I turn them both back on, but that doesn't do it. When I hit the exit command, then it dumps all the data that normally would have gone to the screen.
 
Okay, it turns out the remote system was just responding slower than the termwrite command. The remote system is an immediate response, so its still a little wierd, but thats just the way it works. Anyway I put some waitfor commands and that fixed it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top