|
Mark, FLDCSRPRG is only in effect between your WRITE and your READ. As soon as the user presses ENTER or a command key, control is returned to your program (READ). When you do your next WRITE, the cursor is positioned using the normal rules. So you will have to actively position the cursor to its logical place after a prompt. Simplest method is to have the current position of the cursor returned to you through RTNCSRLOC and reposition the cursor there through CSRLOC. What you probably won't like about this solution is that the cursor will be in the field the user prompted, while you want it to be in the next field. (If only you could write the code for the TAB key into the keyboard buffer ...). That is much more difficult (you'll have to know the next field and will have to use an indicator or know the exact position of the next field) and a lot less robust (a simple change of layout in SDA may have interesting results). Joep Beckeringh ----- Original Message ----- From: "Smith, Mike" <Mike_Smith@RGCResources.com> To: <RPG400-L@MIDRANGE.COM> Sent: Friday, December 14, 2001 7:41 PM Subject: CURSOR POSITION PROBLEM > Hello all, > > I have a screen that has 2 columns of data. The screen is setup using > FLDCSRPRG to control the cursor and direct it straight down the first column > and then over to the second column. > > This works well when i enter data into each field by typing the data out. > However, each column has at least 1 field that has a selection window > attached to it. This is accomplished via an external call with the result > returning to the field. When i Prompt on any of these fields the cursor > positions itself to the first field in the second column. It ignores the > FLDCSRPRG. > > Any ideas on what might be causing this, and how to correct. > > > Thanks > > Mike
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.