RE: Dynamic part on a standard menu

["Booth Martin" <Booth@xxxxxxxxxxxx>]

 I agree Vern, very interesting. You were right of course.  It catches the
phrase at compile time.  I suppose he could compile the menu every time its
called, make it part of the CL.  I haven't tested that solution. 

It is very interesting. 

The other avenue I wondered about but wouldn't have any idea how to do it is
.. have the CL change the color combination of the Client Access session.   
As soon as I saw Mike's mention of the word "Test" it made me remember why I
always set my test environement Client Access Session to yellow characters. 
:)  Been there, been burned.
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: Friday, February 14, 2003 20:30:52
To: Midrange Systems Technical Discussion
Subject: RE: Dynamic part on a standard menu
 
Booth, I don't think that works, either, at least not for dynamic text at 
runtime. The +M() is a MSGCON, which is resolved at compile time. What is 
needed is a MSGID, which would be resolved at runtime - late binding.
 
Even normal indicators would probably not work with a DSPF-type, because 
you have no way to set them.
 
BTW, this isn't for me, but for Mike Wills, who asked the original question.
 
Interesting
 
Vern
 
At 05:35 PM 2/14/2003 -0500, you wrote:
>
>Vern, I tried it too. You're right. External indicators won't cut it. You
>did say you'd accept a CL program to get the menu.
>
>Create 3 message files with the same message number but with your 3
>different messages.
>
>On your Menu SDA (Number 17 in PDM) put a +M (25) on the screen where you
>want the message displayed. It will prompt for the message file. library,
>and MSG Number.
>
>Write your CL to override the message file to the message file that holds
>the message you want displayed.
> In PDM for the menu press F1 and look for +M(nn). It'll explain the
>messages thing there.
>
>I ran out of time to test this, and am worried that the message may be
>snatched at compile time and therefore this solutiion may fail. Still. it
>looks ok
>
>
>---------------------------------------------------------
>Booth Martin http://www.MartinVT.com
>Booth@xxxxxxxxxxxx
>---------------------------------------------------------
>
>-------Original Message-------
>
>From: Midrange Systems Technical Discussion
>Date: Friday, February 14, 2003 16:16:22
>To: Midrange Systems Technical Discussion
>Subject: RE: Dynamic part on a standard menu
>
>Booth, how do you do this? There's nowhere in the SDA opt 2 to condition a
>constant. Putting * in front of a constant only gives display attributes
>and colors. You can always put them into the raw source, but how do you
>turn them on when you are not the app that's calling (using) the DSPF?
>
>Also, I tried U1 in the conditioning indicator location - you can only have
>01-99.
>
>Regards
>
>Vern