I enjoyed the first really hot weekend this spring. It was warming up seriously last week in Munich, and now it feels as if we were suddenly catapulted from a hesitant spring straight into summertime. I also took some time to explore the developer centre and Revit 2013 SDK update, though.
The Revit Developer Center has been updated to a new layout.
The API and the available training material have grown so fast and voluminous that the old layout was getting hard to navigate. I hope the updated site makes it easier still for you to quickly find exactly what you need. Take a look and let us know what you think.
At the same time, the Revit SDK has been updated. If you are using the SDK, I recommend that you immediately switch to the updated version.
Revit 2013 Developer Guide
Some developers asked about the Revit 2013 developer guide, pointing out that it is not included in the SDK in PDF format as it was in previous releases.
The developer guide has been available online for a year and is now 100% on wikihelp. The PDF provided in previous releases was never as up-to-date as the wikihelp location.
More New Revit 2013 SDK Samples
- ModelessForm_ExternalEvent and ModelessForm_IdlingEvent (ModelessDialog)
- ProgressNotifier (Events)
- WorkThread (MultiThreading)
These three all have to do with the enhanced add-in integration supported by Revit 2013, and just like several of the previous samples, they were demonstrated at the DevDays 2011 conferences by the Revit UI API demo sample application, which is available for ADN members together with all other DevDays presentations on the ADN Extranet at adn.autodesk.com under "Events".
The only noteworthy other changes in the updated version are the inclusion of the three new samples plus the UIAPI one to the SDKSamples2013.sln Visual Studio solution file, and the addition of these four plus CompoundStructure to the SamplesReadMe.htm documentation file.
Compiling and Installing the Revit SDK
To compile the new version of the SDK, I had to go through the same steps as always:
2. Compile all the SDK samples using the SDKSamples2013.sln Visual Studio solution. This requires updating the Revit API assembly DLL paths in the project files to whatever version of Revit I have installed. In my case, I still only have the Revit Quasar RP version installed, whereas the project files refer to Revit Architechture 2013, Revit MEP 2013 and Revit Structure 2013.
One way to do this is to use the RevitAPIDllsPathUpdater.exe provided in the SDK Samples folder.
I prefer not to modify the HintPath tags in the project files at all, but rather to simply create dummy directory structures for the three products under the Program Files > Autodesk root folder and copy the required DLLs into a Program subfolder in each of them, ending up with the following seven copied assemblies:
- C:\Program Files\Autodesk\
- Revit Architecture 2013\Program\
- Revit MEP 2013\Program\
- Revit Structure 2013\Program\
- Revit Architecture 2013\Program\
The copy of RevitAddInUtility.dll in the architectural dummy folder is only required to compile the ExternalCommand RevitAddInUtilitySample SDK sample. By the way, the location of this reference is not updated by RevitAPIDllsPathUpdater.exe, like the other two main Revit API assembly DLLs. It would help if the source code for this utility were available.
I also had to change the ProgressNotifier sample Revit API assembly reference paths, which were hardwired to 64 bits.
3. Set up RvtSamples to load all SDK samples into Revit.
To achieve this, I had to set up and install RvtSamples and make a few fixes to the text file it reads to specify the locations of all the samples to load; here is my slightly updated version of RvtSamples.txt.
All in all this is a very clean update with only minor changes required to set it up on my system.
This sample is an external application, not a command, so you cannot test it by simply invoking it via RvtSamples. You have to copy its add-in manifest to the add-ins folder.
Once installed, it disables a command by replacing its implementation with a simple popup message. Specifically, it overrides the Design Options command, thus prevent users from accessing it. It performs the following steps:
- A RevitCommandId is found to match the journal name of the command.
- An AddInCommandBinding is created for this command id.
- An alternate implementation is provided for the command binding.
To run it, once installed, simply start up Revit, open or create a project, and choose the Design Options button on the Manage tab. A popup explains that the command is disabled:
This sample demonstrates how to create a wall category view schedule and display its data on a sheet. It performs the following steps:
- Create an empty wall schedule.
- Add some schedule fields by schedulable field.
- Create new schedule filter.
- Create schedule sorting/grouping field.
- Display a sheet containing the wall schedule.
Run it as follows:
- Open Revit and create a new project based on the default Revit template.
- Manually create a couple of walls with different types.
- Run this command, for instance via RvtSamples > Views > ScheduleAPI.
- A view schedule of wall category and a sheet to show its data are created.
Here is a trivial sample model to test it in:
This is the resulting schedule:
This is a slightly more complex sample that creates a series of stairs, stairs runs and stairs landings configurations based upon predefined hard-wired rules and parameters. It provides an example of how to create and populate stairs elements, e.g.
- Use of StairsEditMode
- Creation of standard stairs runs
- Creation of sketched stairs runs
- Creation of sketched landings
It also implements an extensible structure demonstrating how runs and landings creation can be combined into different stairs configurations.
To test this, start up Revit and open the 'Stairs automation.rvt' sample model. Execute the command, e.g. using RvtSamples > Elements > Stairs automation. Each time the command is run, a different predefined stair configuration is created:
- Single straight stair run
- Stairs/landing combination up to level 2
- Multi-span stairs/landing combination up to level 3
- Single curved stairs run
- Curve stairs run > 360 degrees
As said, a clean and interesting update, and I highly recommend you grab and install it.