Hi Chipp,
Thanks for your reply. I had checked the tabstops. I found the
solution and feel kind of stupid. Guess my age is catching up (87 next
March).
Anyway, For some reason or other I had placed in my library scripts: on
tabKey -> select empty. It did just that!!! Deleted that handler and
all is OK.
We are still hanging in there.
Hope all is well with you and yours.
Regards .. Bob
On Jan 4, 2007, at 10:00 AM, Chipp Walters wrote:
Hi Bob,
Hope you're doing well.
Sometimes developers want the field to 'eat' the tab and advance the
cursor to the next tabstop in the same field. This is why sometimes
the tab doesn't advance to the next field when the cursor is inserted.
Check your tabstops for your fields. If they are not empty, then
that's your problem.
Also, you might want to check and see if your fields are within
overlapping groups. I seem to remember a bug involving autotabbing and
overlapping groups-- though it may have been fixed.
best,
Chipp
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
