This morning saw some lively discussion in the Revit API Panel at the RTC Revit Technology Conference Europe:
Before diving into that, here are some pictures from the conference building window overlooking the Douro River yesterday and during the walk to get here this morning:
Panel Members
- Harry Mattison
- Sasha Crotty
- Jeremy Tammik
I was lucky enough to have Sasha Crotty and Harry Mattison as panel members.
Sasha is the product manager responsible for the Revit API.
Harry is BoostYourBIM (Twitter), an independent Revit API teacher, add-in developer, consultant, and previously also a member of the Autodesk Revit development team.
This represents an ideal combination, bringing in-depth knowledge both from inside the Revit development team and from the point of view of an independent external software developer.
Questions and Answers
[Q]: How to combine BIM with SmartCity? Missing piping functionality? Tools to manage sewerage?
[A]: We are implementing generic functionality. We cannot currently invest in all areas at the same time. Keep telling us what you need. That helps drive the development effort in the right direction.
[Q]: Does the Revit API support inserting a family instance driven from an external database?
[A]: Yes, the Revit SDK includes several samples that demonstrate that kind of functionality, and The Building Coder blog discusses many more.
[Q]: It would be nice to be able to place instances programmatically and still include more interaction, e.g., programmatically select the family and then enable the user to interactively define the exact rotation. This is currently really hard or even impossible to do through the API. You can prompt for points, but you cannot currently display temporary graphics to show what the final instance placement will look like.
[A]: Please put a wish like this on the Revit Idea Station and ensure it gets a lot of votes:
The idea station currently lists over 1300 wishes. We need votes to help prioritise them.
[Q]: Colouring scheme API?
[A]: Put it on the idea station and ensure it gets a lot of votes. We implement things starting at the top of the list. We have strategic directions in which we need to go on one hand, and developer requests on the other, which is quite challenging.
Discussion on the idea station, and existing wish list items…
We have not yet transferred any existing wish list items from the Revit development database to the Revit idea station.
Please submit your wish list items to idea station as well.
There are currently only 22 Revit API related idea station issues.
If you submit a request there that you already submitted as a wish list item, please include the ADN case number, Revit API discussion forum thread URL, the development issue number, e.g., CF-XXXX, etc.
That will help coordinate. There is no need to resubmit all the sample material. Things are moving forward. Lately, several important issues were resolved, some of them really fast.
[Q]: Is there any difference between programming in Dynamo and the pure Revit API?
[A]: No, not really, as far as Revit is concerned. Dynamo is just a wrapper on top of the Revit API via the .NET framework. Dynamo does include other additional exciting functionality that has nothing to do with Revit such as DesignScript and its own geometry kernel. There are currently two versions of Dynamo: a standalone one and Dynamo for Revit, containing Revit-specific nodes and interactions.
[Q]: How does Python interact with Revit?
[A]: Python interaction is implemented using IronPython, which connects the Python engine with the .NET framework and thus provides access to the same, standard, one and only Revit API.
[Q]: Can I access the .NET framework libraries such as LYNC from Python?
[A]: The .NET framework comes with one bunch of libraries, Python comes with a completely different huge set. If you are using Python to interact with Revit, your Python code is on the Python side of the IronPython .NET wrapper and the .NET libraries on the other.
[Q]: Can I use my existing C# Revit add-in functionality together with Dynamo?
[A]: You could to implement your own Dynamo nodes to provide such an access. Alternatively, define some other more convenient place to hook up with existing C# library functionality. Dynamo is completely open source. Please extend Dynamo yourself to implement support for anything that is important to you.
[Q]: Renaming a shared parameter. I implemented a workaround using a temporary shared parameter, deleting the old, adding the new… Is there an easier way, or could one be implemented?
[A]: Be very careful using a workaround like that. You could cause serious problems for yourself. Using the same GUID with a different name can cause serious problems. Multi-lingual apps currently should use separate GUIDs for separate parameter names. We are thinking about implementing an improved global cloud-based shared parameter solution as a web service. That would allow renaming, multiple names for different languages, sharing between companies, global definitions shared across the entire world, etc. You can implement an interim solution as a bridge until this happens. Harry implemented a SQL database solution for handling several of these issues which avoids the need of managing hundreds of shared parameter files.
[Q]: Is there a public roadmap for API changes?
[A]: We don’t have anything API specific. We published an official public Revit product development roadmap yesterday:
[Q]: Purge?
[A]: Harry published some purge code on his blog BoostYourBIM yesterday implementing #RTCEUR API Wish #1: Purging Types and Families.
[Q]: Plans to make Revit warnings more accessible?
[A]: Yes, that access has been implemented in response to wish list item CF-2116 API ability to retrieve Revit Warnings like Manage tab--Inquiry pane—Warnings raised for the Revit API discussion forum thread on warning information for possible release in a future version, as a property on the Revit document class.
[Q]: How can I see what was implemented in the new release, or in an intermediate pre-release?
[A]: We have a beta forum for future development access that provides that kind of information. The Revit SDK is published in intermediate versions during the pre-release phase. That information is updated as we go along and ends up as the final ‘What’s New’ information.
[Q]: How to debug a Revit command without relaunching?
[A]: One simple possibility is to implement your code as a macro, debug, then convert to an add-in. Several other possibilities are discussed in The Building Coder topic group 5.49 on [Edit and Continue, Debug without Restart, Live Development](http://thebuildingcoder.typepad.com/blog/about-the-author.html - 5.49).
Alternatively, use the AddIn Manager. If your add-in is loaded by the AddIn Manager, you can debug it in Visual Studio using ‘Attach to’ the Revit.exe process. That enables you to recompile and reload updated code without restarting Revit.
[Q]: What is the process to convert code between a macro and an add-in?
[A]: The changes are pretty small. Suggestion: always pass in the document as an argument. Then the macro can pass in this.Document to it, and the add-in can use the document instance obtained from the command data argument passed into the Execute method.
[Q]: The debugging situation in SharpDevelop could be improved a little bit…
[A]: Aha.
[Q]: Can you launch a Dynamo script programmatically?
[A]: Yes, you may have to twiddle things. Everything happening between Dynamo and Revit is based on .NET and completely open source. Q; Can I specify the Revit Add-In folder location?
[A]: No. Revit specifies two locations that cannot be changed. You have to place the add-in manifest addin file in one of those. The add-in .NET assembly DLLs can be placed anywhere you like.
[Q]: How to deploy add-ins for other Autodesk products like Robot, Navisworks, etc.?
[A]: You can use the bundle folder supported by the AppStore installation. Look where the AppStore installer puts things.
[Q]: Can we combine our add-in installer with the Revit installer?
[A]: Discuss that with the AppStore team, please. They have more installer expertise than we do.
Notes from Previous Revit API Panel Sessions
Here are some notes from previous similar Revit API panel sessions:
- SD5156 – The Revit API Expert Panel at Autodesk University 2014
- The Building Coder Revit API Panel at the Revit Technology Conference RTC Europe 2015
- SD10181 – Revit API Expert Roundtable at Autodesk University 2015
Session Materials
Here are the PDF versions of the session materials:
