Using the scripts:
After you installed pyRevit and launched Revit, the startup script will find all the individual scripts and creates the UI buttons for the commands.
Just click on the pyRevit tab and click on the command you’d like run. Most command names are self-explanatory but there is a tooltip on the more complicated commands that describes the function.
Some buttons show a black dot after the button name. These buttons have their own configuration. You can open the configuration by Shift-Clicking on the button.
This puts the command in DEBUG mode and will allow the command to print all debug messages. This is obviously really helpful for debugging.
This will show the script file that is tied to this command button in Windows Explorer.
Keeping your library up to date:
Update button under the
pyRevit tab slide-out to fetch all the recent changes from the github repository.
pyRevit will open a window and will fetch the most recent changes from the github repository. Keep in mind that the changes you have made to the original scripts included in the library will be overwritten. Any extra scripts and file will remain intact. After the update, pyRevit will automatically Reload to reflect the new changes.
Every once in a while there will be a core update. But Revit keeps the
pyRevitLoader.dll open when you’re working with Revit and the pyRevit updater can not overwrite this dll.
So the Update tool will checks the commit messages in the pyRevit repository to see if any of them includes
COREUPDATE. This effectively tells the Update tool that there is an core update available and pyRevit needs to be updated when Revit is closed.
The Update tool will show this warning message and won’t update your installed pyRevit repo:
So to update pyRevit when Revit is closed, go to the folder listed in the message and run the batch tool. The batch script will pull and merge the most current pyRevit repository.
After update start Revit again and everything should be good to go.