Ticket #68 ( Closed )

Short Description double-field generating
Entered By: PeteL When: 1998-06-26 13:00:51 Build: 1.03.14b
Categories Type: Problem   Department: Product   Category: HTML Generation
info sent via email - for this one process, code is being auto-filled into a "scratch-pad" area on the 3270 screen. there are about 11 blank lines, each 79 bytes long. after going through this code, one of the lines is displayed as two adjoining fields, the first 28 bytes (size=28, maxlength=79), the second is 51 bytes (size=51, maxlength=51). datastream trace shows no reason for this behavior.
Append By: WindSurfer  When: 1998-07-06 14:10:58  New Status: Pending Customer
Comment Some of this bug is Screensurfer...some yours :)

The template that puts the screen, SCREEN_2F, includes a check for "REASON:" and then puts-out the line with reason in it as two TEAREA tags. Why, we do not know...

Screensurfer was misbehaving by outputting the first input field covering this line with a maxlength that was too big. This logic has been corrected so that the first field put-out will have a maxlength not exceeding the size of the TEAREA requested (which was the bug in the TEAREA).

Screensurfer fix available at ftp://ftp.ieinc2.com/pub/surfer/t1_3_18.zip.

Append By: PeteL  When: 1998-07-07 07:43:32  New Status: Pending IE
Comment oops! i guess i should have traced that, it would have shown up right away in the template trace. sorry about that - if i recall correctly (always suspect), that was done so that I could put focus somewhere other than at the beginning of the line, so they could simply start typing - however, i don't think i ever added the focus logic :(
since your update was part of build 18 and i have backed that out, i'll leave this open until build 18 is stable.
Append By: WindSurfer  When: 1998-07-07 11:16:56  New Status: Pending Customer
Comment Build 18 ready for re-test at ftp://ftp.ieinc2.com/pub/surfer/t1_3_18b.zip
Append By: PeteL  When: 1998-07-07 13:36:04  New Status: Closed
Comment i fixed the code, so i really can't tell for sure that it's fixed, but it isn't broken anymore, so i'll give you the benefit of the doubt.
thanks again :@)