Hmm, I use CNTFLD and WRDWRAP quite a bit and have not see the issue you describe... However, I do not use this with varying fields, normally. Does a display file even support varying fields?
I typically try to make the CNTFLD on the screen LONGER than the actual data fields I'm working with. Wrapping words could fill all five lines on the screen, but with less that the full 250 character of data. By padding extra space on the display field, you can support the full length of your source field (250 bytes).
WRDWRAP only works for I or B type fields, so if this is intended to be for output only, define the field as B and then protect the field to disable input.
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of eftimios
Sent: Monday, October 15, 2007 5:43 AM
To: midrange List
Subject: gap in window border
I have a weird problem in a display file that I need some help with involving a window border.A field inside the window border is defined as: KIQQX 250 VARLEN(100) I use this in the display record using the: CNTFLD(050) & WRDWRAP keywords.This results in 5 lines of 50 characters as a continuous field for a short text field (wonderful!).Unfortunately the border to the right hand side of the first 50 bytes shows a gap in the solid blue: A WDWBORDER((*COLOR BLU) (*DSPATR HI)as does the border to the left of the second line of the 5 lines. That's the only place where this occurs. The remaining three lines have no breaks. I have two colums of blank space between the end of the 5 lines and the border as well as two columns between the border and the start of the 5 lines. Is there more I should be aware of?While I'm at it, is there any web reference which gives a comprehensive tutorial on how to code windows? The only article of use I've been able to find is an MCPRESSONLINE one fro
m 1995! Thanks in expectation.Sincere apologies
This mailing list archive is Copyright 1997-2020 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