Re: [foxboro] WP20 display size constraints

David,

I can't point to a document, but removing grouping will
cut display size, and on the older systems, shave a little
time off callup.

Each group adds at least 1 record to the display file to keep 
track of the group and it's membership.  The first record handles
something like 5 or 6 objects in the group, holds the group name,
base location and size info, and the like. With more objects in
the group, continuation records are used.  Each continuation 
record uses 32 bytes, and keeps track of an additional 14 objects.

Hence, breaking up the groups removes these group and group
continuation record, with the resultant space savings.  The
individual objects in the group remain.  Lots of groups can
mean lots of space saved.

Also, my recollection is that there was a pretty good document 
dealing with display optomization, but it was mainly pointed at
improving time response, not display size.

Y'know, I just got a random thought...  Do you already know 
all this; am I just being a bit too pedantic?

William C. Ricker
FeedForward, Inc.
Marietta, GA, USA
wcricker@xxxxxxxxxxxxxxx
770-426-4422  


 
 
_______________________________________________________________________
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: