[BLDG-SIM] eQuest Text Colors

[Maxwell, Sean]

The eQUEST tutorial from doe2.com explains much of this.  

 

Green is an eQUEST default

Red is a user-defined value

Pink is a user-defined expression

Blue is a user-defined default

Purple is an entry from eQUEST's library - this happens if you use, say,
a default component like a purple that you retrieve from the library.
You can change it (just get past the warning), but if you do, it will no
longer be treated as a library value - that is, it will no longer be
called up from the library each time you load the project.  Instead, it
will become a permanent part of your project.  

 

-Sean

 

________________________________

From: BLDG-SIM at gard.com [mailto:BLDG-SIM at gard.com] On Behalf Of Dan Hill
Sent: Friday, September 07, 2007 9:44 AM
To: BLDG-SIM at gard.com
Subject: [BLDG-SIM] eQuest Text Colors

 

Has anybody seen purple and/or dark blue text in the input section of
eQuest before?  The context being, I have a plenum zone where eQuest is
defining occupancy for this zone.  The occupancy fields are in purple
colored font and eQuest will not let me change them.    And also in some
of my materials the font is a dark blue.  I could use some help
understanding what the colors designate and how to change plenum zone to
having no occupancy.

 

Regards,

 

Dan Hill

Project Engineer, EIT

 

E M C Engineers, Inc.
Email:    dhill at emcengineers.com

 

 
 
==================
You received this e-mail because you are subscribed 
to the BLDG-SIM at GARD.COM mailing list.  To unsubscribe 
from this mailing list send a blank message to 
BLDG-SIM-UNSUBSCRIBE at GARD.COM


===========================
You received this e-mail because you are subscribed 
to the BLDG-SIM at GARD.COM mailing list.  To unsubscribe 
from this mailing list send a blank message to 
BLDG-SIM-UNSUBSCRIBE at GARD.COM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/bldg-sim-onebuilding.org/attachments/20070907/a09916a1/attachment-0002.htm>