Let's look at the Revit macro study results, add-in manager debug/trace functionality and a Python and Dynamo journal analysis tool:
- Revit macro study shareback
- Add-in manager with debug trace
- Journal file analysis
- Plugging the HSL colour format
The results are now in, and we share them with you for further evaluation and feedback:
Feel free to review the research result summary and add any comments or suggestions at:
Revit Macro Study Shareback
You have to set up an account with Autodesk research, fill in a survey and await the response email to see them.
To save others the same process, time and effort, I took the liberty of printing the results to PDF and sharing them here in revit_macro_study_shareback.pdf.
Many thanks to the Revit development team and Siyu Guo for the shareback and interesting results.
We recently mentioned Chuong Ho's open source add-in manager.
Usually, when developing and debugging an add-in with Revit API, user has to recompile, close and reopen Revit each time they modify the add-in code. With Add-In Manager, you can modify and run the add-in directly without closing and reopening Revit again and again.
Chuong announces new enhancements:
Revit Add-in Manager supports Debug/Trace WriteLine including a dockable panel now. It's an improvement that I think will save even more debugging time for programmers 🤗 Download from the RevitAddInManager GitHub repo.
By the way, for the sake of completeness, note that the .NET hot reload for editing code at runtime in Visual Studio 2019 also enables you to update your add-in code on the fly, cf. apply code changes debugging Revit add-in.
Journalysis is a Revit journal, worksharing log and keyboard shortcuts analysis package for the Dynamo visual programming environment. Since there is hardly any documentation on Revit journals, it is a slow process. I have started writing some documentation in the wiki that may not be entirely complete. This package is aimed at automating the analysis of Revit journals and worksharing logs for statistical purposes. It helps track and monitor crashes, API errors, memory usage, sync with central duration, keyboard shortcut usage and more.
Unrelated to the Revit API, I found the 7-minute video explaining and motivating us to switch to HSL colour format very interesting and informative: