Partial passwords

[fp at casabellagallery.com]

Jeff posted:

> 
> > Walter posted:
> > 
> > [ snip ]
> > > 
> > > Hum. For the moment I belive a password edit will
> > work. Why in the world 
> > > can I not devine the password edit? I thought we
> > had something that 
> > > would display "#" since ProFile16 days.
> > > I'm not talking about inputpw... I want a pw edit,
> > or is that a 5.6 
> > > function? I don't need it encrypted, just not
> > displayable.
> > > 
> > 
> > I do not know of such edit but if none exists:
> > 
> > Why not use @wef### trigger + input (@row, at col)
> > pw(10,password) ""?
> > @row and @col are the X,Y just to the left of the
> > actual field.
> > 
> > If I am not mistaken, there is a new argument for
> > input that a default
> > value can be given thus setting your input variable
> > to whatever the 
> > real field is.
> > 
> > After obtaining your input, you can simply check
> > number of characters
> > in input field (pw in this case) and display as many
> > # as needed.
> > 
> > Of course, a little of work is needed to make sure
> > that you ALWAYS
> > display ####### in lieu of actual text so, a dummy
> > variable should be
> > used on your screen while the real field is kept in
> > the background.
> > 
> > Between @entsel, @wlf### and possibly automatic, I
> > figure about 6 to
> > 10 lines of code.  Oh, do not forget to 'skip' out
> > of your @wef### trigger!
> > 
> > Hope this points you in the right direction!
> > 
> > 
> > ---
> 
> Jose, I don't follow.  How do propose to get the input
> without echoing the characters to the screen?  Did you
> mean to use a popup update - instead of an input?
> 

I think that using   'inputpw'   will do the trick.  After
I posted previous message I noticed I had typed "password"
as an edit (was thinking of what the original poster was
looking for) so I typed wrong command.

I just looked up 'input' and found that 'input_popup' is the
one that uses 'default' as a parameter not 'input'.  

Other than loosing the ability to default its content, you
can still get the job done:

 13  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
@wefpx ? If:                                                                   ?
       Then: px(10,*); inputpw ("3","18") pw(10,*) ""                          ?
 14  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       ? If: pw ne ""                                                          ?
       Then: pn=""{pw{""; px=repeat("#",len(pn)); display                      ?
 15  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       ? If:                                                                   ?
       Then: 1=pw; display; skip                                               ?
 16  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -

Field 1 is my real field
Field px is a dummy field opened on screen placed on X=3, Y=19

Since I am placing my input X,Y at ("3","18"), the content of px is kept on screen
and it will appear that it is overwritten as you type ... So, it works out pretty 
well after all.

NOTE: This kind of code will cause a loop if the ONLY field on the screen is that 
which is triggering the code ... Make sure you have a 2nd field so that 'skip' sends
you there!

Give this a shot and see if it is good enough for you!

Regards,



Jose Lerebours