Paweł Romaniuk has shared his workflow to take various parameters from a model, run the necessary algorithms and then write the area back to a parameter for use in a Revit schedule. Link to pdf download is below… Thanks Paweł.
There is no immediately easy way to override the colour of an entire Revit Link. Of course, you can set up a View Template and override all of the individual subcategories, but that can get time consuming when working with many links…
Worksharing Display Mode gives us a quick way of visualising Worksets. What if we put each Revit Link on its own Workset? Then if we set Worksharing Display Mode to Worksets, these Links are overridden with the Workset colours selected in the dialog:
Unfortunately, the Worksharing Display Mode setting is a temporary override (notice the border around the view?), and it will be switched off when we close and open the file. However, the colour choices will be retained. Is there a way we can quickly ‘turn on’ the Worksharing Display Mode for all views in the document? Perhaps this could be done just prior to printing, or at the start of an editing session?
Enter… you guessed it… Dynamo.
I made a node to Enumerate Worksharing Display Modes available, and another one to Set Worksharing Display Mode for View. Finally, I adapted the archi-lab Get All Views node into a List All Views node. Now, we can set them in one click:
And a Screencast:
Each time you print, you will be prompted to “Leave the mode on and print…“, but the colour override will print fine 🙂
Update: Colours will transfer using Transfer Project Standards, as per: Transfer Project Standards
If you populate a project with the desired worksets, usernames, and colors you can automatically transfer most of this data over to another project. Under Manage > Transfer Project Standards, there is a new option for Worksharing Display Settings.
Keep in mind this will not transfer over workset names from one project to another.
It will however transfer over workset colors, should the same name workset appear in both projects.
It is pretty difficult to change the Workset of Pipe Insulation. The Properties Palette allows you to change them one at a time (but not multiple), while the method I posted about previously can change multiple Pipe Insulations to a different Workset, but it didn’t have a nice filtering mechanism.
Enter Dynamo… I made a custom node that takes a list of Pipe Insulations and gives you the Host Pipe element:
Then, I packaged this up in another node that collects all Pipe Insulations, checks their Workset, finds their Host Pipe, and then saves those Pipes to a SelectionSet:
So, if you have Pipe Insulations on the wrong workset: 1. Install Bakery package in Dynamo 2. Run definition as in image above 3. Close Dynamo 4. Load the Saved Selection 5. Group these Pipes (which groups the Insulations too) 6. Change workset (it will have already adopted the current workset) 7. Ungroup 8. Done
Thanks to Konrad and Andreas for archi-lab and Clockwork packages respectively. I get a few comments about my Bakery package having a lot of dependencies, but I like the fact that I just need to install Bakery and I get archi-lab, Clockwork, Lunchbox etc. Its like a rough and ready deployment solution…
Oh, one more thing. You may notice in recent versions (like 0.8.2 RC) that there is now some custom path management for Dynamo resources:
This uses the Media Creation Tool. I was running Tech Preview build 10041 on one of my devices and it wasn’t automatically getting the Windows 10 RTM upgrade, so I used this method instead of waiting for Windows Update…
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 think its safe to say that Dynamo package deployment is still a work in progress, particularly when considering issues of intellectual property along with the complexity of IT networks in large organizations. For that reason, any step to make Dynamo easier to deploy and use is a good idea.
Dyno Browser gives us a very simple way to share and view DYN definitions using a certain file structure and the Roaming directory inside a user’s profile.
Start Dyno Browser from the Dynamo ribbon dropdown (Visual Programming)
Right-click in the pane and select “Open Workspaces Storage”
In this folder, make a new top level folder and then put some DYN files in it, like this:
Once we have some DYN files in the right location, we can right-click in Dyno Browser and select “Rescan Workspaces Storage”. This will update the list of available definitions in the Dyno Browser pane.
Now, right-click on the definition you want to run and select “Open Workspace in Dynamo”
You may not see your definition straight away, so just press the X button on the Start tab to close that tab. Your definition should now be visible
So, what is good about this? Because now we can create a shortlist of important or ‘approved’ DYN files and deploy them using the appropriate file structure to the team, using Roaming profiles.
There is actually a bit more functionality available in Dyno Browser: it supports using JSON to feed certain preset values to Dynamo nodes. This is a bit more in-depth, and can be review at the home page.
After Google Reader was decommissioned, I was happy to find that inoreader was an excellent replacement. But one feature was missing: free and easy RSS Feed Translation. Did you know you can deploy your own Google Script to translate RSS feeds, and then subscribe to them in your preferred RSS Reader (like inoreader?)
Here are the steps, from labnol.org:
Open the Google Script and choose File -> Make a copy to create a personal copy of that feed translation script into your Google Drive.
Replace the source language (line #4), the target language (line #7) and the RSS feed URL (line #10) with your own values. (some language codes here)
Go to File -> Manage Versions and choose Save a new version. You may leave the description field blank.
Go to Publish -> Deploy as Web App, choose “Anyone, even Anonymous” under “Who can access the app” and click the Deploy button.
Google Script will now offer you a link to the web app. That’s actually the new URL of the translated RSS feed which you can directly subscribe in Google Reader or any other news reader app like Reeder, Flipboard, etc.
If you wish to translate another RSS feed, or offer the same feed but in another language, just go back to step #1.