[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2977.0. "Move pointer in a field" by BERN01::BIGLERC () Wed Jul 07 1993 16:04

Hello

im looking for a solution for my problem how i can move the cursor in a 
field.

As pre-function i load a given value into the field and i want to move the 
cursor just behind the last character i inserted (see picture).

  Field X:  0228________
                ^
      	        | Cursor

Can anybody tell me the easiest way to do this.

I have a ALL-IN-1 V 2.4 System english, FMS 2.4 and VMS 5.5-2.

Thanks in advance

  Chris
T.RTitleUserPersonal
Name
DateLines
2977.1Can't be doneSCOTTC::MARSHALLSpitfire Drivers Do It ToplessWed Jul 07 1993 16:139
I don't think you can do this, as it's all controlled by FMS.  All ALL-IN-1
does is tell FMS which field to go to next.

Do you want the user to be able to change the prefix value you've put in the
field?  If not, you could make the prefix part a separate, display-only field,
and have the enterable part right next to it.  Then the cursor would appear in
the right place, but the user wouldn't be able to backspace over the prefix.

Scott
2977.2BRUMMY::MARTIN::BELLMartin Bell, NTCC, Birmingham UKWed Jul 07 1993 16:365
Chris,

	would a RIGHT-JUSTIFIED field do what you want?

mb
2977.3Thanks! A question more....BERN01::BIGLERCThu Jul 08 1993 07:5728
First thanks for the quick replys.

Scott

>Do you want the user to be able to change the prefix value you've put in 
>the field?  If not, you could make the prefix part a separate, display-only 
>field, and have the enterable part right next to it.  Then the cursor would 
>appear in the right place, but the user wouldn't be able to backspace over 
>the prefix.

Yes the user should be able to change the prefix. I tried this to make two 
seperate fields, but the problem is as you describe you can't change F13 to 
delete the current field, go one field back an delete this also. This key is 
controlled from FMS. 

Martin

>would a RIGHT-JUSTIFIED field do what you want?

No exactly but i think this is a way to make the input for the user a little 
bit comfortable.

Do anyone now if it's possible to call a FMS Form Driver routine from 
ALL-IN-1 or VMS ? There is one routine, called FDY$AFCX, with this you can 
choice insert/overstrike mode and positioning the cursor into the field.


Thanks Chris
2977.4I doubt that you'd have the information you need...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeThu Jul 08 1993 10:3612
    Guessing, I expect that you'd need to know addresses of our FMS
    internal data structures to enable you to call the FMS routine, and I
    don't think they are visible even in a CLI.
    
    Still, perhaps you should wish for this, since it's been asked for
    several times before.
    
    I wonder how it might work:
    
    	/GET_SAVE = #symbol /CURSOR=????
    
    Graham
2977.5Thanks for the answers !BERN01::BIGLERCThu Jul 08 1993 11:5114
Graham

>/GET_SAVE = #symbol /CURSOR=????

This occurs a -LIB-F-SYNTAXERR by LIB$PARSE. And there is a . before CURSOR.

When you try to use this command on the field by the command mode FMS 
ignore this.

I think the best for me is to use a RIGHT-JUSTIFIED field.

Thanks for the replies.

Chris
2977.6Don't try this at homeSWAM2::RHODEWALT_BRI am a talking parrot.Wed Jul 14 1993 00:2415
    I once did this the hard way. Under 2.2 or 2.3, we used the tab
    terminator to kick off a little Fortran program (I think I used COMMAND
    -- sheesh!) that prompted the user for input on the same line, three
    columns in from the beginning of the field. Once in the program, I
    simulated all the usual FMS actions. On termination, the program wrote
    the prompt result into the FMS field, with three spaces stuck on the
    front, and moved on to the next field.
    
    The effect was that the user could "indent" within a field. As I
    recall, they were satisfied and used it.
    
    When I think about it now it reminds of driving my dad's car too fast
    and other dangerous teen-age behavior that I somehow survived.
    
    Bruce