WEF brwlooks - no cursor

[Jay R. Ashworth]

On Fri, Sep 07, 2007 at 12:13:31PM -0400, Kenneth Brody wrote:
> Quoting Jay R. Ashworth (Fri, 7 Sep 2007 11:42:52 -0400):
> >I'm tempted to report this as a bug, but (as so often happens) maybe
> >it's just me (so many things are just me<tm>):
> 
> I'm not sure what part of what you described could be called a "bug",
> nor what a "fix" would involve.

I know: fixing it would be a wart.  The fix would be "if a brwlookup is
called from WEF context, skip the code which turns off the cursor".

> [...]
> >When filePro pops up a browse lookup, it turns off the text cursor.
> >Normally that's ok, since you watched the cursor enter the field in
> >question, then hit F6 manually, so you know where you are.
> >
> >If you WEF it, though, you never see the cursor enter that field.
> >
> >I know I can manually position the browse, but is that all people do
> >when they do this?  Is there some other way to make clear which field
> >you're popping up for?
> 
> I wrote this code some time back, which hilights the current field:
> 
> ::end:
> @wef*::gosub hilite ; end:
> @wlf*::gosub lowlite ; end:
> ::'''''''''''''''''''''''':
> hilite::show (@ro, at co) "\r" & fieldval(-, at fd) & "\r" ; end:
> lowlite::show (@ro, at co) fieldval(-, at fd) ; end:
> 
> Perhaps use something like this as a wrapper wround your brwlook?

I ended up, actually, repositioning the popup right overtop of the
field; it works well enough.  I actually don't spend a lot of time
coding programmatic brwlooks; this is the first time it's come up for
me.

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274