Re: Help: Need word-wrapping ability in screen arrays

Liam Grieser (lgrieser@crash.cts.com) wrote: : My Environment: : AT&T 3B2 and HP9000 Unix boxes : Informix Software: : Currently running Online Engine Ver. 4.10.UC1, : SQL Ver. 4.10.UC1, : 4GL Rapid Dev. Ver. 4.10.UC1, : I-Star TCP/IP Ver. 4.10.UC1 : Problem: : I am trying to create a screen that contains two screen arrays with the : ability to word wrap. Unfortunately, each array will only have : five lines showing on the screen, yet can contain 200 lines of : data. I find this unfortunate because the manuals tell me that the word : wrapping ability is allowed only if the whole array can fit on the entire : screen. To clarify my problem, I should correct the above. The form will have two multiline fields that could be wordwrapped, but only if all of the lines for each field could fit on the screen (according to the Informix manuals). An example of my abbreviated form specification file: SCREEN { SUBJECT: [f001 ] [f001 ] etc... COMMENTS: [f002 ] [f002 ] } end TABLES tablename ATTRIBUTES f001=tablename.field1 TYPE char; f002=tablename.field2 TYPE char; Unfortuately, each multiline field will only show five lines but can hold as many as 200 (I speculated using a screen array only because it would be necessary for the user to scroll through them to see the full text of the fields. Since screen arrays cannot word wrap, I proposed the following possible solution. : If word wrapping can't be done for the situation described above, : one of my primary alternatives is to allow the user to *view* the contents : of the screen arrays, but if he/she wishes to add or edit any : information to it, he/she will need to indicate so on a nearby field : which will make a call to a third party editor. I could write my own : word wrapping program to get around my problem, but I would prefer : the user have the full screen to add or edit data as well as : having the automatic word wrapping already built in. : Unless anyone can tell me different, it seems the alternative mentioned : above would be the most viable alternative. If so, does anyone out there : know of a ASCII word processor for the Unix environment that is device : independant, is public domain, and the source code is available (in case : I need to make any minor modifications)? I'm sure this can't be a new problem as It seems that this situation would occur in many types of applications. Perhaps I'm looking at this in the wrong way and Informix has a simple solution to it! I'm sorry I wasn't more clear the first time I posted! Thanks in advance for any help you might provide! lgrieser@cts.com Liam Kieran Grieser - A truly international name!