The @when user key function/feature.... Wish list item?

John Esak john at valar.com
Wed Oct 27 22:49:08 PDT 2010 

Well, funny, very similar... But because it was a row oriented screen that
people could put their cursor into any field and do pretty much any thing,
*including* the push-down/ull-up thing.... I had to work in a set of
specific Cursor placement directions.  Sometimes their cursor had to stay in
the same field, other times it had to go into the next field or previous,
etc., etc.  So, after all the various subroutines happened or didn't, I had
to determine where to leave them sitting. So in the end additional code had
to be implemented to  not only decode which field they left, but where it
was in the order of the row,column scheme.    Eventually, I think I got this
all down to a very neat set of code.  However, if the @wukA* could have been
available, it would have been hundreds of lines shorter.   I don't think I
want to post a 500 line table up here.  Besides, it is really Tim's
property, I was on salary to him when I wrote it.  But, come to think of it
, that shouldn't be a problem to him, because I had to do it all as a CALL
table so I could use the NOAUTO option.  Tim's main INPUT table is thousands
of lines of code and uses up nearly every 2 character variable.  I had none
left to put on the screen full of of columns and rows.   So what I mean is,
it wouldn't be disclosing any of his proprietary code.  Maybe I'll ask if I
can find it and show it here.


John

P.S. By the wa, I wasn't asking for just @wuk*, which of course would be
nice.  I was asking that the * (wildcard) take effect wherever I put it in
the label.  Such as @wukA*, @wukB*, etc.  Then, I could at least have
written more column oriented code.  Also, it would be the same with @wuk15*
or @wuk2**.  The enhancement would be smart enough to fill out all the
fields until the next higherdecade or centenary number.  (is that a word?
Well, hopefully it is understood.  @wuk2* would cover from field 200 up to
but not including 300, and so forth.




> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Bruce Easton
> Sent: Thursday, October 28, 2010 12:18 AM
> To: filepro-list at lists.celestial.com
> Subject: Re: The @when user key function/feature.... Wish list item?
> 
> Something maybe like:
> 
> @wuk*  If:
>         Then:  kh(1,*)=@fd; gn(2,.0)=asc(kh)-"96"
>              If:   gn ge "1" and gn le "15"
>         Then:  goto (gn) of wuka,wukb,wukc,wukd . . . .
>              If:
>         Then:  end  'or other handler
> 
> Bruce
> 
> 
> > George,
> > This is almost exactly what I did do. But, realize I had 7 
> columns of 15
> > rows and that many fields to individually chec k.  It 
> worked fine, but was
> > not a simple copy and paste thing.  That's a lot of code to 
> write for a one
> > liner of @wukA*.   But thanks.  I'll post my version of this if you
> > like....I took more than 2 minutes on it... So it is better. :-)
> >
> > John
> > ~
> >
> >> -----Original Message-----
> >> From: flowersoft at compuserve.com [mailto:flowersoft at compuserve.com]
> >> Sent: Wednesday, October 27, 2010 10:29 PM
> >> To: john at valar.com; filepro-list at lists.celestial.com
> >> Subject: RE: The @when user key function/feature.... Wish 
> list item?
> >>
> >> Now, I only spent 2 minutes on this... :-) but wouldn't the
> >> code (from INPUT
> >> of course!) do what you are asking for?
> >>
> >> @wuk*	  If: @fd="a"
> >> 	Then: goto WUKA
> >> 	  If: @fd="b"
> >> 	Then: goto WUKB
> >> 	  If: @fd="c"
> >> 	Then: goto WUKC
> >> 	Etc., etc., etc.
> >>
> >> -----Original Message-----
> >> From:
> >> filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
> >> [mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.c
> > elestial.com]
> >> On Behalf Of John Esak
> >> Sent: Wednesday, October 27, 2010 7:13 PM
> >> To: filepro-list at lists.celestial.com
> >> Subject: RE: The @when user key function/feature.... Wish 
> list item?
> >>
> >> This is a little off this thread, but who cares.
> >>
> >> On the apps where I push an pull rows up and down with
> >> @wuk... I often use
> >> arrays of 2 char dummies on the screen for the different 
> rows/files.
> >> Generraly, they look like:
> >>
> >>
> >>
> >>     *aa     *ba     *ca
> >>     *ab     *bb     *cb
> >>      *ac    *bc     *cc
> >>      ...    ...     ...
> >>      *aj    *bj     *cj
> >>
> >> Everyone knows this routine and probably uses this sort of
> >> thing all the
> >> time.
> >>
> >> What would be so good is if there were a way to wildcard each
> >> group of two
> >> letter variables for the @wuk feature.
> >>
> >> It would be nice to be able to write:
> >>
> >> @wukA*    if:
> >>          then:  blah blah
> >>
> >>
> >> @wukB*
> >>
> >>
> >> In fact, this might even be nice for at when
> >> leafving/entering as well, but
> >> not so much perhaps.
> >>
> >>
> >> In any case. Is this something that could be accomplished
> >> easily the way you
> >> now handle labels and such.  I don't see why not really, but
> >> of course,
> >> that's why I'm asking. :-)
> >>
> >> John
> >> `	
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> >>> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
> >>> m] On Behalf Of Kenneth Brody
> >>> Sent: Wednesday, October 27, 2010 4:37 PM
> >>> To: rkreiss at gccconsulting.net
> >>> Cc: filepro-list at lists.celestial.com
> >>> Subject: Re: The @when user key function/feature....
> >>>
> >>> On 10/27/2010 4:06 PM, Richard Kreiss wrote:
> >>>> Interesting as I had not realized this would work.  Tested
> >>> it and it does.
> >>>> I still would like and @fkey(function key pressed,
> >>> @afkey(alt&   function key
> >>>> &   @cfkey(ctrl&   function key) function that works like @key.
> >>>>
> >>>> This might make all 12 function key available or maybe just
> >>> 1-10 and then
> >>>> alt 1-9 and ctrl 1-9 for a total of 28 available function
> >>> keys.  This would
> >>>> make 54 possible single key options available especially
> >>> now with dokey for
> >>>> doubling up some built in key functions.
> >>> [...]
> >>>
> >>> Well, for *nix systems, the limits on termcap makes it
> >>> impractical to add 48
> >>> keys to each entry.
> >>>
> >>> However, for Windows, you can set PFSKHEX=ON, and @SK will be
> >>> a 4-digit hex
> >>> value for any "unknown" keystroke.
> >>>
> >>> -- 
> >>> Kenneth Brody
> >>> _______________________________________________
> >>> Filepro-list mailing list
> >>> Filepro-list at lists.celestial.com
> >>> Subscribe/Unsubscribe/Subscription Changes
> >>> http://mailman.celestial.com/mailman/listinfo/filepro-list
> >> _______________________________________________
> >> Filepro-list mailing list
> >> Filepro-list at lists.celestial.com
> >> Subscribe/Unsubscribe/Subscription Changes
> >> http://mailman.celestial.com/mailman/listinfo/filepro-list
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > Subscribe/Unsubscribe/Subscription Changes
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> >
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list

More information about the Filepro-list mailing list