× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 21/12/2005, at 2:35 AM, Vernon Hamberg wrote:

Doug, I find the WRDWRAP keyword to be generally unusable. It does not do anything on input when used with a CNTFLD keyword. The field does wrap on output when I had both WRDWRAP and CNTFLD.

CNTFLD and WRDWRP will wrap on input when used with an emulator that properly supports the feature. The only one I know of is PC5250. Mochasoft's emulator doesn't support any of the advanced DDS GUI features. It tells the system it doesn't support them and the system converts the data stream to a character-based variant which is why WINDOW and SCRBAR etc. work but are rather ugly just like they are on an older Twin-ax device. The various other emulators seem to cherry-pick the DDS GUI features and only support some of them. There are 3 defined levels of 5250 GUI support in the specification but emulators can ignore specific settings within those levels.

On a non-CNTFLD field it did wrap on input - nice enough. Only problem is that the extra spaces at the end of one line become part of the field. And this happens when both CNTFLD and WRDWRAP are used, too - the field gets changed without user input! NASTY!

True, the filler spaces that cause word-wrapping become part of the data but that's by design. The intention is that data is formatted during input and used untouched on output. Imagine the case of a memo field where the user can type 8 lines of continued text that will be printed verbatim on an output document such as a policy. The output fields should simply map the input field. This avoids the print program having to do word wrapping because it was handled during input. The only complication is that you need 8 separate fields in the printer file but mapping a data structure over the single input field will solve that.

Another surprise (I think these are documented) is that you cannot insert if you are on the first character of the second line (the one after the wrap). I was able to insert when on the end of line 1, but as soon as I got to line 2, no more insert.

Insert worked for me on any of the lines in a CNTFLD/WRDWRP field as long as there is space on the following lines to insert into. In my testing I had empty space (as in never typed into--nulls not blanks) on the second line of the continued field and I could insert text on any of the 3 lines in my test field. Interestingly if I inserted text at the start of the 3rd line my new inserted text was automatically shifted to the previous line when I typed a space as long as the inserted word was small enough to fit in the available nulls at the end of the previous line. Seems to work pretty well for a character-based device. The only awkwardness I found was destructive backspace wouldn't shift from the first position of the 2nd line to the last position of the 1st line.

However I think few sites actually use the WRDWRP support even if they use CNTFLD which also seems infrequently used.


Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.