Announcement

Collapse
No announcement yet.

Elaborating Legends

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Elaborating Legends

    We typically try to keep field information to a minimum - it reduces time spent on data entry, and allows us to align to our specification without constant drawing & schedule revision - however of late, there's been contests to that in terms of visual output (I know, I know... :banghead: )

    Essentially, certain people in our office want the legends to explain EVERYTHING - so :

    FIRE CLASS :
    A
    B
    C
    doesn't satisfy them - "they" want :

    FIRE CLASS :
    A - yadda yadda yadda
    B - yack yack yack
    C - yawn yawn yawn
    But obviously that stretches out data entry in our fields... which I've so far stopped them from changing - but has seen text notes used alongside the legends, in views, used for the descriptions! :crazy:

    Is there a way for legends to report any more content? Would I at least maintain some sanity constructing these "keys" in a legend view? Can I even do that? (away from Revit at the moment)

    There has to be a better way!

    #2
    Use Key Schedules... A being the Schedule Key, "yadda yadda yadda" being the well, yadda yadda yadda...
    Martijn de Riet
    Professional Revit Consultant | Revit API Developer
    MdR Advies
    Planta1 Revit Online Consulting

    Comment

    Related Topics

    Collapse

    Working...
    X