×
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 11/08/2010, at 4:01 AM, Booth Martin wrote:
Here's the code:
But where is the WINDOW keyword?
61 WDWBORDER((*COLOR GRN))
62 WDWBORDER((*COLOR YLW))
WDWTITLE((*TEXT &W1TITLE1) +
*RIGHT *TOP)
WDWTITLE((*TEXT &W1TITLE2) +
*LEFT *BOTTOM)
It all works fine. Does just what I want it to do.
Excepting for one irritating thing. I like the default borders
instead
of the colons, and this does that just fine excepting in one scenario.
The colons and dots are the default character border. Certain graphic
devices (e.g. PC5250) under certain conditions (when the full width of
the window including leading and trailing attribute bytes is contained
completely within the length of a screen row and ENHDSP(*YES) is
active for the display file) will replace the default character border
with a set of so-called Graphical elements which give the illusion of
a drop-shadow border made from various vertical and horizontal lines.
So I presume your problem is that on some display cycles you see the
desired "graphical" border and on later display cycles of the same
screen you see the character border.
Does indicator 62 control other attributes of the window?
Do you have display size condition names (*DS3 or *DS4) specified on
the WINDOW keyword?
What values have you specified for the start line and start column and
how many rows and columns does the window occupy?
The first exfmt works right, either with 61 or 62 on.
However, if 61 is on, and I refill the screen with 61 off and 62 on,
then everything still works, but the border goes to the colons.
Presuming your window satisfies the requirements for displaying
"graphic" border characters then I suspect you would have better
results with:
61 WDWBORDER((*COLOR GRN))
N61 WDWBORDER((*COLOR YLW))
although I'm not sure why without seeing the 5250 data stream that
would be generated in both cases.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
