Re: [foxboro] 'Group' Visibility with DM

On slower systems or on pc's running Exceed these rectangles which hide the 
complete object might sometimes respond slowly, which creates a messed up 
screen, but we use it as wel. If the objects are similar (buttons etc...) I 
create it once, then copy it a number of times, each time with another group 
name.(to localise it in the .dmp file) Then use the d_edit command to change 
all C:B references from 1 object in 1 go, so you don't have to configure 
each item, only one configuration setting per object. Works fine for me. Or 
if you call up the screen form a button on another screen, and this first 
screen determines which button should be visible on the second screen, you 
can use $variables on the second and declare you're variables on the first 
screen, works fine as wel and requires only one object.

I tried converting DM's to foxview once on a test station...ran into so many 
layout & font problems we should have edited each graphic manually, which is 
not a temping thought. After a lot of work we would then be able to run our 
existing DM graphics in foxview... with the old DM layout! Why bother? If we 
were to setup a new system from scratch I would probably go for Foxview, 
seems the logical way to go in that case. Our operators are familiar with 
the layout of the DM's, and allthough the graphics are very "crowded" and 
have an "oldfashioned" look they do not object to it. But I must admit the 
foxview graphics look more up to date and "flashy", but "looks" are not the 
most important reason to switch to Foxview.

Rgds,
Dirk Pauwels - DCS coordinator
Engineering dept.
Hexion Specialty Chemicals
Coatings & Inks division
E mail: dirk.pauwels@xxxxxxxxxxxxxx


>From: "John W. Smith" <wb4lbg@xxxxxxxxx>
>Reply-To: foxboro@xxxxxxxxxxxxx
>To: <foxboro@xxxxxxxxxxxxx>
>Subject: Re: [foxboro] 'Group' Visibility with DM
>Date: Mon, 25 Jul 2005 11:29:20 -0400
>
>Yeah, that's what I was afraid of.  It's been a long time since I worked
>with DM on a daily basis and that's the way I would have done it 'back in
>the day'.  I was just hoping someone might have a better (easier) idea.
>
>Thanks!
>
>JWS
>
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx
>[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Johnson, Alex P
>Sent: Monday, July 25, 2005 9:12 AM
>To: foxboro@xxxxxxxxxxxxx
>Subject: Re: [foxboro] 'Group' Visibility with DM
>
>
>In the DM, you have to tie visibility to each piece. DM doesn't provide a
>mechanism to add attribute control to a group.
>
>
>Regards,
>
>Alex Johnson
>Invensys Systems, Inc.
>10707 Haddington
>Houston, TX 77063
>+1 713 722 2859 (voice)
>+1 713 932 0222 (fax)
>+1 713 722 2700 (switchboard)
>alex.johnson@xxxxxxxxxxxxxxxx
>I hope to see you at the Invensys Process System User Group meeting October
>3-6 in Houston, TX -
>www.invensys.com/usergroup2005
>
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
>Behalf Of John W. Smith
>Sent: Monday, July 25, 2005 7:30 AM
>To: foxboro@xxxxxxxxxxxxx
>Subject: [foxboro] 'Group' Visibility with DM
>
>I've got a graphic where certain pieces of equipment need to 'disappear'
>when they are not being used and other pieces of equipment need to appear 
>in
>their places when being used.  This would have been a piece of cake in
>Foxview but I can't think of a good way to make it happen with Display
>Manager.  I really don't want to set visibility on each line, arc,
>rectangle, etc. if I don't have to.
>Anybody got a better idea?
>
>Thanks!
>
>John W. Smith
>Automation Engineer
>Global Automation Partners
>
>--
>No virus found in this outgoing message.
>Checked by AVG Anti-Virus.
>Version: 7.0.338 / Virus Database: 267.9.4/57 - Release Date: 7/22/2005
>
>
>
>-- No attachments (even text) are allowed --
>-- Type: application/ms-tnef
>-- File: winmail.dat
>
>
>
>
>_______________________________________________________________________
>This mailing list is neither sponsored nor endorsed by Invensys Process
>Systems (formerly The Foxboro Company). Use the info you obtain here at
>your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
>foxboro mailing list:             http://www.freelists.org/list/foxboro
>to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
>
>_______________________________________________________________________
>This mailing list is neither sponsored nor endorsed by Invensys Process
>Systems (formerly The Foxboro Company). Use the info you obtain here at
>your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
>foxboro mailing list:             http://www.freelists.org/list/foxboro
>to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>--
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.0.338 / Virus Database: 267.9.4/57 - Release Date: 7/22/2005
>
>--
>No virus found in this outgoing message.
>Checked by AVG Anti-Virus.
>Version: 7.0.338 / Virus Database: 267.9.4/57 - Release Date: 7/22/2005
>
>
>
>_______________________________________________________________________
>This mailing list is neither sponsored nor endorsed by Invensys Process
>Systems (formerly The Foxboro Company). Use the info you obtain here at
>your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
>foxboro mailing list:             http://www.freelists.org/list/foxboro
>to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>

_________________________________________________________________
Bescherm je Inbox: Phishing - hoe te herkennen, rapporteren en voorkomen    
http://www.msn.be/security/phishing/

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: