home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: bit.listserv.sas-l
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!wupost!psuvax1!atlantis.psu.edu!drh4.psu.edu!drh4
- From: Daryl R. Hoffman <drh4@apix.psu.edu>
- Subject: Re: Cursor Position in FSEDIT Called from AF
- Message-ID: <ke31Huotwb@atlantis.psu.edu>
- X-Xxmessage-Id: <A76F53437901399C@drh4.psu.edu>
- X-Xxdate: Tue, 5 Jan 93 22:01:23 GMT
- Sender: news@atlantis.psu.edu (Usenet)
- Organization: Pennsylvania State University
- X-Useragent: Nuntius v1.1.1d12
- References: <921230211359_76666.136_CHL73-1@CompuServe.COM>
- Date: Tue, 05 Jan 93 19:58:47 GMT
- Lines: 59
-
- Subject: Cursor Position in FSEDIT Called from AF
- From: Patrick Spreng, 76666.136@COMPUSERVE.COM
- Date: Wed, 30 Dec 1992 16:14:00 EST
- In article <921230211359_76666.136_CHL73-1@CompuServe.COM> Patrick
- Spreng, 76666.136@COMPUSERVE.COM writes:
- >SAS/FSP and SAS/AF Version 6.07
- >
- >Amnon Igra writes:
- >
- >> I am using the call fsedit function in a SAS AF SCL program. When I
- use it
- >> without specifying a screen, then the cursor automatically is placed
- on the
- >> first variable in the default screen, and the tab key takes the cursor
- to the
- >> next variable just like I want it to.
- >>
- >> When I specify a screen, and then modify the screen using SAS FSEDIT
- screen
- >> modify menu, I no longer get the cursor to work as before. I don't
- think I
- >> should have to write another SCL program in FSEDIT. Can anyone help me
- figure
- >> out why the cursor no longer responds to the tab key, and why it no
- longer is
- >> initially placed on the first screen variable? Thanks very much!
- >
- >I know of two ways to change the cursor position. One is
- >documented on page 269 of "SAS/FSP Software Usage and
- >Reference." The CURSOR command is entered while you are in the
- >FSEDIT window and changes the default cursor position used each
- >time an observation is displayed.
- >
- >The other way is to add the CURSOR SCL statement to the INIT
- >section of your program. This is documented on page 134 of
- >"SAS Screen Control Language Reference." This is the method
- >that I use when I'm developing FSEDIT applications called from
- >SAS/AF version 6.07 under MVS.
- >
- > FSEINIT:
- > return;
- > INIT:
- > cursor wvarname;
- > return;
- > MAIN:
- > ...
- >
- >I hope that this is helpful in your situation of SAS 6.04.
-
-
- I believe that what Amnon was asking is why is the default cursor
- position not being set when he uses a permanent user defined screen, and
- it was set when he used the SAS FSEDIT default screen. The cursor should
- be positioned on the first field of the screen, unless the applications
- programmer specifies otherwise. I have not had any problems with this in
- SAS 6.07 running with VM/ESA 1.1.
-
- The cursor command is the way to make sure that the user is placed on
- the appropriate field, and Bruce has answered that.
-