i think of "Suppress Error Messages" as nettalks own 'simple' debugging device and not really for what we think of as messages,
these are messages under nettalks control, You are speaking of messages from other parts of clarion.
messages from things like abc and system messagaes need to be avoided/intercepted - see prop:messagehook.to roll-your own.
To save time and effort i use Capesoft's Messagebox template. it can hook all the messages (from message, halt and stop).
That will work for any message generated from your clarion app.
What i do for any web/service type app,is set a global default to hook all messages to automatically clear after a few seconds,
and to log all messages to a UILogfile.log. Which when i am developing or running in application mode, is good enuff
for debugging interactively, But for services where messages are hidden or the server is not accessible to user, the messages clear automatically
and i have a record of events that may need to addressed without the app freezing.
the goal for a service app is to have NO messages, however i tend to let messages flow,i will add in extra messages to document
some unexpected/ unusual occurence, the effect on users is slowing down by the length of time the messagebox takes to automatically clear
but i end up with a definitive log of what happened and when. (if and when i address the issue, the app also appears to speed up!)
poul
Topic: Suppressing messages (Read 3117 times)