bill@hao-wks.UCAR.EDU (Bill Roberts) (11/17/87)
Recently I started using LSC. I'm using the 'fopenw' function create a new
"console" window. I understand that 'fopenw' does not make the new window the
current window. Stdout is initially the current window. So I thought I could
use 'setwindow' to make my new window the current window.
I get my new window displayed over the stdout window but the new window cannot
take any input. That is, the stdout window is catching all input. In fact my
new "console" window isn't even active and is over laid with the small console
window (the one that sez close me or hit return to kill the console window).
What am I missing. Thanks for any input.
--Bill
UUCP: {hplabs, seismo, nbires, noao}!hao!bill
CSNET: bill@ncar.csnet
ARPA: bill%ncar@CSNET-RELAY.ARPA
INTERNET: bill@hao.ucar.edu
"... the Eagle Wing palace of the Queen Chinee'"singer@endor.harvard.edu (Richard Siegel) (11/17/87)
In article <956@hao-wks.UCAR.EDU> bill@hao-wks.UCAR.EDU (Bill Roberts) writes: >I get my new window displayed over the stdout window but the new window cannot >take any input. That is, the stdout window is catching all input. In fact my >new "console" window isn't even active and is over laid with the small console >window (the one that sez close me or hit return to kill the console window). It's not clear how you're getting your input. We do know that there is a bug in fgets() that caused input to be echoed to the console window instead of to the current window, and that has been fixed in an internal revision. --Rich **The opinions stated herein are my own opinions and do not necessarily represent the policies or opinions of my employer (THINK Technologies, Inc). * Richard M. Siegel | {decvax, ucbvax, sun}!harvard!endor!singer * * Customer Support | singer@endor.harvard.edu * * Symantec, THINK Technologies Division. (No snappy quote) *