Re: On-Message trigger works?

From: Dan Glasstetter <glasstetter_at_bmcwest.com>
Date: 1995/06/30
Message-ID: <glasstetter.90.000FB7FC_at_bmcwest.com>#1/1


In article <dsulliva.28.2FF42A08_at_AFIT.AF.MIL> dsulliva_at_AFIT.AF.MIL (David J. Sullivan) writes:
>From: dsulliva_at_AFIT.AF.MIL (David J. Sullivan)
>Subject: On-Message trigger works?
>Date: Fri, 30 Jun 1995 16:44:57 GMT
 

>I want to capture the messages on the status line of the console window and
>display them elsewhere. (Status line is too small at the resolution we
>are designing in.) The On-Message trigger at the form level seems to fit the
>bill, only problem is it doen't work. Am I doing something wrong, or am I
>barking up the wrong tree? Details follow.
 

>Dave
 

>Trigger text (From level ON-MESSAGE trigger):
>:button_bar.status_line := MESSAGE_TEXT; (display item in button_bar block)
 

>Forms info:
>Form 4.5.6.0.7 for Windows

We use a form procedure to handle the situation you describe. Although this won't truely capture your "message" statements, it can be used in place of them.

  • start procedure code -----------

Procedure Put_Message (Msg_Txt IN Char) Is

-- 
-- Moves messages into pop up alert
--
-- Alert "MESSAGE_ALERT" must be defined
--
-- Use Put_Message('message text') instead of MESSAGE('message text')
-- Use in ON-MESSAGE Trigger
-- 
Alert_Id Number;
--
Begin
  Change_Alert_Message('Message_Alert',Msg_txt);
  Alert_Id := Show_Alert('Message_Alert');
End;

--------  stop procedure code -------------------

To make this a little more generic (but also more cumbersome to call) you 
could not hard code the defined alert "MESSAGE_ALERT", but pass it in as a 
parameter.   

This procedure has become a standard at our site, so we use 
PUT_MESSAGE and MESSAGE_ALERT exclusively over MESSAGE on the status line.

Hope this helps !

Dan Glasstetter
Senior Analyst/Programmer/DBA (it's a small department)
BMC West Corp.
Boise, Idaho
glasstetter_at_bmcwest.com
Received on Fri Jun 30 1995 - 00:00:00 CEST

Original text of this message