Today I helped a colleague (a very talented one at that) with a small issue around a PMTRCD and usage of multi-line edit for oversized fields. Something he hadn't seen before.
He was confused as to why his data entry field was showing on the device design and not showing when executed.
Figure 1 shows a mock up of his device design looking pretty standard.
Figure 2 shows the same screen at run-time. Note the cursor has positioned to the field acting strangely but the underline is not showing.
If you want to recreate this issue I created a file as follows (See Figure 3 and 4) :-
Additionally, in the device design we set the long field to multi-line Y and set it to 4 rows and 50 wide.
To resolve the issue was a case of applying a (clearly little known) trick of moving the multi-line field over by one byte. (Figure 5)
This then allows the run-time screen to paint properly. (Figure 6)
Any takers on providing the technical explanation? as a compare source doens't seem to highlight a clear and present danger. (Figure 7)
I've always nudged these over by an extra byte for years and years but I guess some tips and tricks get lost.
Thanks for reading.
Lee.