I know it's 15 years later and this is the ultimate necropost.

Here in 2020 I'm having the same problem with tabs in wordwrap fields in a 4gl form (but for me it happens in both insert and overwrite modes). Did anybody ever come up with anything regarding it? I'm using 4gl version 7.51.FC1XD.

Thanks!

Roderick Schertler

On Tuesday, March 8, 2005 at 9:36:19 AM UTC-5, Doug Lawry wrote:

HP-UX B.11.11 / INFORMIX-4GL 7.30.HC6

We have found a 4GL bug in which actual tab characters can be inserted into a screen field and subsequently into the database. It only happens under exactly
the following conditions:

1) The field is multi-line (defined as WORDWRAP on the form)
2) Character insertion mode is active (Ctrl-A key)
3) Tab is pressed

There are 88 forms affected, so I really want a generic fix so I don't have to
put in a work-around in all the 4GL modules. Any ideas?

Also posted to: [email protected]

--
Regards,
Doug Lawry
www.douglawry.webhop.org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Mostly answering my question as stated I found this on page 4-186 of the 4gl reference manual (version 7.32, 4gl statements > statement descriptions > input multiple-segment fields):

TAB enters a TAB character in insert mode and moves the cursor to the next
tab stop. This action can cause following text to jump right to align at a
tab stop. In typeover mode, this key moves the cursor to the next tab stop
that falls on an intentional character, going to the next field segment if
required.

What I was really looking for was a way to override this behavior. "on key (tab)" works in other fields but not the word-wrapped one.

- Roderick

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)