Hi all...
Consider me a dummy here...
I do not want any code or for anyone to show me how to do it at this time, but here is the question:-
I have had this brainstorm to be able to control the AudioScope.sh program in the "Shell Scripting And Programming" forum...
Is it possible, by piping say, for me to be able control the AudioScope in its termianl from a separate terminal in REAL TIME using the INKEY$ idea to change parameters whilst it is scanning?
This would give me parallel control instead of sequential serial control.
I do not mean like inputting data on the second terminal and sending it, but instead, terminal one polling the second terminal say after each plot and having the ability to change TB and SHIFT for example whilst in the same scan...
I hope this makes sense...
Again just a yes or no and something of what to type into Google say...
TIA...
Terminals don't poll anything, programs do.
I'm not sure I get the idea. What could two terminals talking to one keyboard do, which one terminal talking to one keyboard couldn't?
Are you thinking maybe, display a menu in one window, and scan continuously in another?
Hi Corona688...
Ignore my last I think I can use KB control during the scan(s) in _REAL_TIME_ without the second terminal...
Thanks for attempting to undestand my gibberish.
The idea was to use the second terminal as a control panel with pseudo-buttons that activated upon pressing a relevant KB character, (INKEY$), sending that character to the main terminal to be acted upon. But I think there might be enough room by overwriting the status window in the original code with small buttons. The idea was to use the second terminal to control external stuff too without affecting the first terminal and if the link was broken the local access by the first terminal would be unaffected and still active...
So FTTB I will take look at the new idea...
You could also make the terminal bigger... I'm not sure whether OSX terminals support the resize command or not...
Hi Corona688...
It does and I have already used it...
Look way back in the early days of the AudioScope thread and you will see that I used it then removed it later...
I tested it on several terminals and shells and on some it doesn't work so I decided against it...