Announcement

Collapse
No announcement yet.

"Title Block", "Title Sheet" or something ELSE?

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

    "Title Block", "Title Sheet" or something ELSE?

    One of my latest efforts has been to make our "Title Block" families a bit nicer - in terms of wanting to make them more of an assembly of elements, that can pulled together in different configurations, for different jobs - for different paper sizes etc.

    My first attempt has been to make the "title block family" exactly what the category suggests it should be - the title block (as opposed to the sheet entire) - and use a generic annotation family nested within it for the paper/medium itself.

    But (and this may be because it's the end of the day) I'm starting to slow up on how/where to take things next.

    Since you can't have title block families loaded into one another, and we are still going to want to read the project parameters, it's not like we can use other categories to make "an address block" "a logo block" "a keyplan block" (like we once did with you know what) - so I'm thinking have I reached the end of the road already?

    I guess I could make a super family, full of vis parameters, different sized fonts, and loads of rules... but should I bother?


    #2
    I use nested Gen Anno familes for many of the different things on the ttl block. Seals, Stamps, Logos... I am in the process of making it more Parametric right now. 1 Family that coveres all sizes and configurations. I think this makes it eaiser to use.
    -Alex Cunningham

    Comment


      #3
      Originally posted by Alex Cunningham View Post
      I use nested Gen Anno familes for many of the different things on the ttl block. Seals, Stamps, Logos... I am in the process of making it more Parametric right now.
      Which is how I've done it to date for "static" information (disclaimer, copyright, logo, address block, etc) but there's the "read/edit through" ability (from the project environment) that's got me kind of stumped...
      Originally posted by Alex Cunningham View Post
      1 Family that coveres all sizes and configurations. I think this makes it eaiser to use.
      Totally agree, so are you tying in loads of associated parameters to the "host" ?

      Comment


        #4
        made my sheet size parametric, standard sizes as instance y/n parameters. never again purge a titleblock that you'll need to reload a minute later! try out different sheet compositions on the fly! make changes to all titleblocks in one family! took some work, but no regrets. just remember to pin the origin-defining lines, that filled regions don't play nice and curse autodesk for not letting us use shared labels and shared family parameters in the same family.
        There must be a better way...

        Ekko Nap
        Professional nitpicker, architect, revit consultant, etc.

        Comment

        Related Topics

        Collapse

        Working...
        X