iraf.net

>From bart@fornax.jpl.nasa.gov Tue Nov 12 17:03:16 1996
From: Chris Simpson <bart@fornax.jpl.nasa.gov>
Subject: Re: xc problem
To: fitz@noao.edu (Mike Fitzpatrick)Thanks, that worked fine. Now I have another problem -- reading the
image cursor. When an attempt to read the image cursor is made
(e.g. by typing =imcur from the CL or doing i=fscan(imcur,x,y,i,s1)
from a script), nothing is supposed to happen until a key is pressed.
Now, however, I find that =imcur returns "EOF" immediately, and
similarly, the value EOF is assigned to i in the above line of script.I got the feeling that this might be a result of an ungraceful exit
from a cursor read earlier in the day, but logging out of IRAF and
back in didn't help.Any ideas?Cheers,
Chris>From fitz Thu Nov 14 13:00:34 1996
To: bart@fornax.jpl.nasa.gov
Subject: Re: xc problemHi Chris,
At first I thought the problem was your use of the string variable
's1' (it should be a struct variable like 'list'), but it didn't seem to
make a difference. For some reason I don't understand I can sometimes make
the imcur read hang when using SAOimage as the server, but not with XImtool.
Which were you using? I couldn't ever get it to return EOF immediately
though, it would always attempt a cursor read. You might check that your
'stdimcur' environment variable is set to 'stdimage', and that 'stdimage'
is a defined frame buffer (imt512, imt800, etc).Cheers,
-Mike