Update Method 1: after seeing my post, Troy Wright kindly shared his take on this. It uses only one custom node – Eraser by Julien – and it also works for Revisions that have been ‘ticked’ as issued, so this is probably the more powerful method.
As always in Revit, it leaves behind the first row in the Revision Schedule… However, this method is more robust than deleting Revision Clouds as it also removes items appearing based on the “Revisions on Sheet” schedule. It is also much faster than laboriously using the Merge Up command one by one in the Revision Schedule.
I don’t think the API programmers should get scared just yet, but is there a day coming when visual programming will completely replace custom code? Julien seems to think so:
“I firmly believe Dynamo could be used for many many purposes, and addin-like behavior is one… Definitions are easy to share and update. Users can tune them with only some basic Dynamo skill. It is not the same with addins. It is a lot of work to manage and deploy. And users will not be able to tune things. Same thing for macros.”
Sometimes you just need to hear an idea and you innately know “this is going to be useful…”
Quick Select command for Autodesk® Revit® to select by element type and its properties. Expand the element or family type and select the properties that you wish to filter by. Click OK and all those elements will be selected.
When in “Or” mode, the command will select all elements that match any of the properties.
When in “And” mode, the command will only select elements that match all the selected properties.
Example of potential uses:
select all Casework on a particular Level – done
select all Filled Regions with a given area – done
select all Walls whose Top is Attached – done
As with most addins I post about – its free. Download on Exchange at: this link
If you didn’t like my Random Trees in Revit post (which actually exposes the opportunity for randomizing and scaling any form or import in Revit), then maybe you will enjoy some of these other random landscape generation methods. Read on below:
Ever wanted to get a Tag to pick up the hardcoded Elevation value given to a nested Family? Then check out this great little thread and cool answer by Julien!
Answer: You need to set a SP in the nested family. Make the plate geometry attached to ref planes that are not the 2 from the template. Assign a SP to the distance between the RP at center of geometry and the RP that defines origin. SP will be by instance. Beware of directions for correct behavior when loaded in the host. In the host family, add the same SP, select the plate, and in properties palette, look for the tiny button on the left. Click and choose the SP you’ve added. The insert point of the plate must be set to the ref level of the host. Now you have the elevation of the plate driven by a SP in the host. Create a tag for this SP. You’re done.
Remember Julien Benoit’s adaptive component tutorial from a year ago (link here)? Well, Julien has made something pretty cool and posted it on RFO. It is basically a 4 point adaptive component that calculates the area of the resulting surface using Bretschneider’s formula.