× 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.


  1.  Home
  2. MIDRANGE-L
  3. April 2013

Re: CL command creation

Hi, John:

Study Chuck's sample code. Only one MONMSG per variable, at least as far as MCH3601 is concerned.

That's what I was talking about.

Mark

> On 4/12/2013 6:50 PM, John Yeung wrote:
Mark wrote:

Not just "first touch" but EVERY touch. =-O
Vern wrote:

Read my other reply to Joel - the MONMSG need only appear
one time, with controlling variables for whether to do any further
processing - easy - peasy - see, I HAVE written these things
and do know what I'm doing. At least one way of doing it.
Having more than one MONMSG per variable seems excessive to me. If
I'm reading Vern correctly, you judiciously do one MONMSG the first
time you touch a parameter; if that first touch triggers the message,
you know not to touch that parameter again. But if the message
doesn't come up, there's no harm in touching it again. You can
structure your code accordingly.

John


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.