Experimental Physics and
Industrial Control System

John William Sinclair <[email protected]> · Thu, 19 Mar 2015 11:08:41 -0400

See

http://ics-web.sns.ornl.gov/edm/info/show.php?mon=Apr&theDay=24&year=2009

On 03/18/2015 07:45 PM, [email protected] wrote:

I start EDM with a command like this:

   edm -x -ctl UI:Alert main.edl

Then the large display described by main.edl appears.  When I write
'alert.edl' to UI:Alert, the smaller message described by
alert.edl pops up, floating over the large display.

But then, other activities can cause the large display to cover the
message.  I try to raise the message to the top again by writing
'alert.edl' to UI:Alert again, but instead I get a new window also
displaying alert.edl, in addition to the older one (which is still
obscured under main.edl).  Each write to UI:Alert creates a new
window.

I see this behavior when I write alert.edl to UI:Alert via OUT from an
scalcout record, or when I command: dbpf UI:Alert alert.edl in the
ioc shell.

When I write alert.edl to UI:Alert and the message pops up, dbgf
UI:Alert always shows an empty string (not 'alert.edl' as I
expected).

I see this behavior when UI:Alert is a stringin, or when it is a stringout.
In both cases, I define it this way, without any explicit field definitions:

   record(stringin, "UI:Alert") {
   }

Is there anything I can do so that writing to UI:Alert will raise an
existing display to the top, instead of opening another instance of
the same display?

Alternatively, is there some other way to force a display to the top, or
(better yet) create the display so it always remains on top?

Jon Jacky

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System