Re: WDWBORDER changing to colons unexpectedly.

Booth,

What do you mean "default borders" vs. the colons?

Assuming you mean the GUI border....check the size of the window vs.
the text you're displaying.

The GUI elements require a couple of extra spaces vs. the character elements.

Assuming the you've got ENHDSP(*YES) on the CRTDSPF, then the system
will use the GUI border unless you've not given it enough room to do
so at which point it switches to the character border.


Try making the window a bit bigger or your title fields a bit smaller;
but note that if you make the window too big and you'll never get the
GUI border:
http://groups.google.com/group/comp.sys.ibm.as400.misc/msg/810dba344f2d7a99?hl=en

HTH,
Charles


On Tue, Aug 10, 2010 at 2:01 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

Here's the code:
        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 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.

Any ideas?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.