Another bug with legend views

[patricks]

Well my boss and I just discovered another bug relating to legend views.

We typically use a numbered symbol annotation family to note things on drawings where text notes would not fit, and then do a filtered note block to list all the annotation numbers and notes.

The note block schedule is set to NOT itemize all instances, because obviously we don't need to see the same note for every instance of the annotation. In the schedule, any note that is not placed somewhere in a project view will not populate the schedule.

Now to the problem: instances of our note family placed in Legend views ALSO do not populate the schedule! I'm guessing this is related to the bug about Select All Instances of any particular family will not pick up instance in legend views (dimensions, text, etc.) which is already problematic enough.

If you navigate to the note type in the Project Brower, right click on a note type that is only placed in Legend views, the Select All Instance option is grayed out, as if it's not being used. So I guess this could be why it's not populating the schedule.

I just submitted a SR on this, but I wanted to let people know about it.

[Scott D Davis]

I think its because anything placed in a legend view is not scheduled. Legend views are basically just "snapshots" of objects or annotations and are set up that way so they don't get counted or quatified as being part of the model.

[twiceroadsfool]

It also makes sense, as its a Legend view. Its kind of a lousy situation: You need to be able to put a SYMBOL in a legend for a SYMBOLS Legend, and you dont want THAT instance to count as being used.

But then you want to NOTE things in legends, using SYMBOLS, that dont count as being used, lol.

+1 for Previous Phase Legends. Ever since we started using them weve never looked back.

There are only 4 "Revit Legends" in out projects. The symbols Legend, the Material Hatch Legend, the Partition Hight Notation legend, and the Keynote Legend.

The rest are live views in Annotation Phase.

[patricks]

I think its because anything placed in a legend view is not scheduled. Legend views are basically just "snapshots" of objects or annotations and are set up that way so they don't get counted or quatified as being part of the model.

Scott, we have a window type legend view in which we have several repeating notes for each window type. Not all notes apply to all windows, though, but some apply to multiple windows. This is why we're placing a note symbol with A, B, C, etc. with a note block containing all the notes. Do you have any other suggestions for making this work other than an actual "annotation" previous phase like Aaron uses?

This project is pretty far along in CD's which is why I'd rather not get into Annotation phases on this one, but I may bring that up to my colleagues as a possibility for future projects.

[twiceroadsfool]

I know it stinks to change things mid-project, but consider this:

It wont affect the stuff you have done already, and you can just do it for the stuff you still need. AnnotLegend and AnnotDemo. Just make sure everything created in AnnotLegend gets demolished in AnnotDemo (we keep a 3d view just for this pupose). Then it wont effect anything else in the project, besides exports to non-phrase-friendly-add-ons.