(Sorry for the long interruption in blogging - project work was just too heavy to devote time to blogging).
I ran into something interesting yesterday that I had not seen before, and I figured it was worthy of a quick blog post. When doing Revit-oriented development, there are a lot of times when you check the type of an element, and have logic in place to handle that element based on the type.
I was running an application that I had tested before in the past - but it was no longer working - why? And then I stumbled upon an interesting quirk about Revit Architecture versus Revit MEP - something that I had never encountered before:
For certain types such as Pipe, when you ask Revit what type it is - the answer depends on which flavor of Revit you are using. In the sample above, I was interrogating a pipe element. In Revit MEP, it tells you it is a Pipe. BUT - with the same model in Revit Architecture - it tells you that it is an "Element" (Revit's code word for generic elements that don't have any special definition).
The element's category is consistently reported as "Pipes" - but this is just the first time I've ever noticed the type of object being different based on which flavor of Revit you're in. It makes sense that Revit behaves this way - if it did not, you would be exposing a variety of properties and methods for this type of object which should only be available in MEP.
In any case - just be aware - the code that you have that works perfectly one way in MEP could work completely differently in Revit Architecture (and I'm sure this is not the only scenario).
Sunday, October 11, 2009
Monday, July 20, 2009
We finally got our Avatech Utilities for Revit launched a month or so ago. We've added to the list of utilities as well:
- Room Renumber
- Change Case
- Space Update (New)
- Grid Select (New)
- Door Mark Update
- RevitCity Content Browser
- Earth Connector
- Room Phase Copy (New)
Unfortunately - we came to a hard decision... because of the amount of effort it takes to produce, support and update these utilities on an ongoing basis - we have to start charging money for them.
Because we didn't really give any warning on this - we wanted to make this as fair as possible for the 2010 release.
As such, we did the following:
- Avatech Utilities for Revit LITE - this will continue to be free (it's made up of the top four utilities above).
- Avatech Utilities for Revit - will be offered for $395 USD / seat
To take care of all of the people who had previously downloaded the software- we've put in a one-time program to give previous downloaders 5 standalone seats of the software (this was sent via e-mail to the address which was registered during the download). You should have received the second and final notice of this program today (so if you're thinking "where was that?" you might want to check your junk mail folder or something like that).
Finally, there will be other special offers for customers who purchase their Revit software through Avatech (which I realize is only a fraction of the total audience - sorry!).
While this has been a bit tough for us to work through - I'm looking forward to what this means - we should be able to do a better job growing and releasing more utilities in the future.
I apologize! I've committed the cardinal sin of blogging - not doing it once you got started.
But you know how it is - work gets busy, yadda, yadda, yadda.
In any case - I think it's back to a level where I can blog occasionally... and I'm looking forward to it. Now if I can just remember all the ideas I had while I've been "away".
Posted by Matt Mason at 9:01 AM
Friday, May 08, 2009
Hi there, readers...
Today is the last day of public voting for the Autodesk University 2009 conference...
I've submitted three classes and I'd REALLY appreciate your vote:
- Deep Dive on the Revit API: Advanced Topics
- The Power of Creation in the Revit API
- Check It! Building Check Plugins for BIMreview
You can vote at:
Saturday, March 14, 2009
(Part of the What’s New in the Revit 2010 API series)
The Geometry area of the Revit API has a few interesting and helpful enhancements in the 2010 version.
While there was previously a HermiteFace class to represent the surface – we now have a HermiteSpline element for the splines that can be created (which will probably result in many more HermiteFaces as well – since it only takes one button to go from spline to face).
The HermiteSpline exposes its control points and tangent vectors (nice touch). WARNING: For those of you who have been using Tessellation – like we have on our Earth Connector application – be prepared for an explosion of points as Revit Users start using splines. The 5-point spline shown above tessellated into 287 points… (I probably have to start investing some mental energy in a “reduce” function – because that’s pretty heavy!).
As I joked about in one of the previous posts – Autodesk has finally broken down and added the Point concept to Revit (yes, yes – the XYZ class was there before – but Points are now first class geometric objects).
The reference points in the picture above are part of the spline, but it is possible to create standalone ReferencePoint elements – and the geometry extracted for the reference point is a Geometry point.
I have not yet figured out why it’s important to have a point in the geometry class (since you can get the location directly from the element) – but I’m sure that there is a good reason (consistency, if nothing else, I suppose).
Making Life a Little Easier for You
Historically if you dealt with geometry in the Revit API, you had to brush up on your linear algebra in order to deal with Transformation matrices… For example, a chair might be modeled within a family centered on the 0,0,0 point – but then it gets placed 100 times into a project way out in space. Every instance has a transformation matrix that gets you from the “internal” geometry locations – also known as the “SymbolGeometry” – out to the actual geometry location in the project.
It was even worse when items are nested a few levels deep… I know that, for example, stairs have railings and railings have balusters – and balusters gave me fits for quite some time, being a good number of levels deep.
Autodesk started making this better a couple of releases ago – making it easier to get the transformed version of things – and they’ve taken it another step now.
(Instance is the Geometry class which represents things like FamilyInstances, and other elements where you need to dig into the definition of things). Both of these methods can optionally take a transform matrix to transform – or just give you the easy answer.
The Hit Reference
I mentioned in “Very Spatial APIs” that the Reference class has been upgraded, mainly to provide the additional information retrieved when shooting rays through elements. The new properties:
- ProximityParameter (how close the hit is to the origin)
- Element (the element that was hit)
- FOREIGN (from the docs: “The reference is to geometry or elements in linked Revit file.”)
- LINEAR (curve or edge)
- GeometryObject (the geometry intersected)
- Transform (of an instance, if that’s what was hit)
- UVPoint (U,V parameters of the face, if that’s what was hit)
This is yet another area with modest but solid improvement in the API in 2010.
(Part of the What’s New in the Revit 2010 API series)
The Event section of the API is one area that I believe developers have been hoping for years to see more… In 2010, Autodesk re-writes a bunch of what is there, adds a few more interesting events – but probably leaves out what you were hoping for…
Before and After
The biggest change, both for the re-written events and the new events is that they can receive callbacks either “before” the action or “after” – which is a very nice, mature feature for events. The “before” events enable you to either (1) fix the model before it is saved/printed/etc OR (2) stop the process and ask the user to do something before the action can be performed.
NOTE: for those of you who are thinking immediately about having “alternative interfaces” for something like Document.SaveAs – I think you’ll be disappointed. So far as I can see all of the “before” events are still fired after the user has completed the dialog (i.e. chosen the new SaveAs target file) – but before it actually happens.
User-Driven and API-Driven
I’m not sure that this was the case in the past – but there are notes with the 2010 release that indicate that the events will fire not just when triggered by interactive usage – but also when triggered by the API. I’m not 100% sure if I love that (once we developers all start using them at the same time) – but we’ll see.
The following events have been re-implemented:
- Document Creation
- Document Opening
- Document Saving
- Document Save As
- Document Closing
- DialogBox showing (Revit 2010 generally uses the newer style “TaskDialog” from WPF, rather than the old-school “MessageBox” of the last 15 years)
The New Events
The new events are:
- File Export
- File Import
- View Printing
- Document Printing
- View Activating
- Document Save to Central
The last one, saving a document to the central file – has some interesting options – including being able to see the exact properties that have been used for the operation, including:
- Compact Central File
- Relinquish Borrowed Elements
- Relinquish Family Worksets
- Relinquish Project Standard Worksets
- Relinquish User Created Worksets
- Save Local File
That said, alas, they are read-only.
I know you were hoping for an element-level event. Autodesk knows that you’d like to have it – but there are apparently some complexities and pitfalls to giving us this power (not the least of which is that we could probably cause never-ending cascading update loops).
All in all, though – the events took a good step forward in terms of the maturity of the API. They’re better thought out than before, and they’ll get more usage.
Monday, March 02, 2009
(Part of the What’s New in the Revit 2010 API series)
Revit 2010 introduces a number of nice enhancements to Importing and Exporting in general – and best of all (for developers, at least) – all of the new capabilities are also available through the API.
The ADSK File Format
One of the new exciting capabilities in 2010 product line revolves around a new file format called an ADSK file (Autodesk Exchange File). This is essentially a zip file, but it contains all the geometry and data that are needed to support DIFFERENT intra-Autodesk software workflows (including, for example – Revit to Civil3D and Inventor to Revit).
The BuildingSite export gathers a wide variety of information useful primarily to Civil3D users, and puts it together in a package that’s easy to transfer.
The content includes:
- dwg files for the footprint, building shell, site plan and property lines.
- Data such as:
- Gross Building Area (based on a selected AreaPlan)
- Building Model data (doors, floors, roofs, etc)
- Project Information, including:
- Location information
- Building Type
- Total Occupancy
- Area per person
- Preview Images
All in all, the amount of XML data is significant in there – so I think we’re just hitting the highlights of what is potentially transferred here…
The API export gives a few options, and I think between what it picks up automatically from the model and what you can specify, you have access to pretty much everything.
Import from Inventor
Import from Inventor is another incredibly important workflow in the greater scheme of things – particularly for the MEP side of things. The ability for manufacturers to model their content in Inventor (with as much detail as they want) – but then to easily produce lower-detail models for use in Revit (including MEP connectors) – that’s powerful.
I haven’t gotten Inventor 2010 installed yet – so I haven’t tried out the export side. The import side seems to be pretty minimal (both in the UI and in code). But the capability is there.
(NOTE: I can’t recall if these are DWG or ACIS solids – but I’m pretty sure it’s not a “new” method of exchange – it’s a better-controlled, better-wrapped version, which includes additional properties and the MEP connectors – but the geometry is probably on the “heavy” side compared to native Revit).
Export to DGN
New with Revit 2010: export to Microstation DGN format. The export options include:
- Export Solids (ACIS or Polymesh)
- Layer Mapping (a layer setting or file)
- DGN Template File
This is equivalent to the new “Publish –> Share with Autodesk Seek” capability. The capability in the UI packages up a piece of content, along with XML to fully describe the types, the parameters, etc – all a part of the PartAtom specification used by Autodesk Seek.
The API version of this only produces the XML file – you’ll have to do the rest yourself. NOTE: This method, ExtractPartAtomFromFamilyFile is on the Application class (not the Document or Family class).
The GBXML export is much improved in the 2010 User Interface (shown below).
The most important new capability to note here is the “Export Complexity” option. This option will control how much detail is exported to the GBXML model from your Revit model – ranging from only the basics, to how “shading surfaces” are handled, to whether curtain wall mullions are counted as shading surfaces.
The capability for the API to export GBXML was introduced in the prior version – but this has been updated to include the all-important complexity option.
NOTE: This is technically not a change to the “Export” method for GBXML, but a change to the GBXMLparamElement which defines the export options.
This is a fascinating new addition to the Revit MEP package – the ability to read GBXML back into Revit. While I’m sure that there is probably more workflows that I haven’t quite grasped yet, just being able to use Revit as a GBXML viewer (or see what went out the door as GBXML) seems very useful.
The API exists for import, however, there are currently no options.
New DWF Export Options
The API has been restructured a little around DWF export – shaping up for more robust options in the future (for example, there’s now separate options classes for DWF2D, DWFX2D, DWF3D and DWFX3D) – although they’re mostly the same between DWF and DWFX at present.
In the 2D DWF/DWFx export, they’ve added support for controlling:
- Image Format (compression level)
- PaperFormat (size)
- Paper Orientation (portrait or layout)
These additions will help fine tune the DWFs you can create.
Most of the Export Options (DWF and FBX) also now include a “StopOnError” option, so that it won’t keep going if it runs into a problem… sounds like a good idea! :)
Many of the enhancements to import/export are driven by the core 2010 product enhancements. But it’s so nice to see that they’re investing in keeping the API up with what’s new, rather than lagging a year or more behind.
Saturday, February 21, 2009
One of the most exciting areas of potential API development is checking the building… Whether trying to determine if the egresses are short enough, or whether there is a nurses station close enough to each room, or just understanding how buildings, floors and rooms are modeled – there are a lot of things to check for. Historically, these things have been hard to check for – it was far easier to just look at a drawing than to try and figure it out.
But all that is beginning to change with some neat new APIs in 2010, which give you some tools to help understand the building and spatial relationships between objects.
One of the classic CAD solutions to these kinds of problems is “shooting rays” through your model… That is, set a point and a vector, then see what that “ray” hits. This was kind of possible with some creative math prior to 2010 – but it’s both better and easier now in 2010.
The new mechanism:
Document.FindReferencesByDirection( origin, direction, View3D)
The new method returns back an array of references – and the reference class has been upgraded to include:
- Type of Reference (Surface hit, Element hit, Edge, Foreign, Mesh)
- GeometryObject of the hit
- XYZ location of the hit
- Distance of the hit from the origin (“Proximity Parameter”), UV location of the hit on a surface (if appropriate)
Important Note: The View3d that you specify controls a few things – first, if you’ve got elements or categories hidden, those do not seem to be “hit”… Also, remember that if you’ve got model phases, the ray will follow the phase of the view.
Still, it’s a great new feature for those who are trying to use the API for any kind of building analysis.
Where am I?
The other enhancements in the category of spatial awareness relate to being inside a particular architectural room or MEP space. If you want to test if a given point is in a known room or space, you now have:
- Room.IsPointInRoom( xyz )
- Space.IsPointInSpace( xyz )
Conversely – if you don’t know where a particular XYZ point is at all, you can ask:
- Document.GetRoomAtPoint (xyz)
- Document.GetSpaceAtPoint (xyz)
I think these enhancements are also critical… while FamilyInstances have long known which room they were in – these API enhancements give a great variety of additional power for analyzing buildings.
(Part of the What’s New in the Revit 2010 API series)
As with each release of the Revit API, there are a ton of enhancements to the “Elements” area of the Revit API. Whether it’s new capabilities on existing elements, or new Element classes to make Revit elements more identifiable and understandable – enhancements here are a big deal.
Elements and Materials
One of the features I’m most excited about is the new Element/Material part of the API. In the past, trying to do material take-offs with the API was tough – especially if the designers were using Split Faces (which almost everyone does). You pretty much had to export out to ODBC or schedules to Excel in order to extract what you needed. But no more.
In Revit 2010, every Element has a Materials property to show all the materials associated with an element. Further, you can call Element.GetMaterialArea( Material ) or
to get the area or volume of material for that element. With this, people trying to do material take-offs through the API should be in far better shape!
For a number of releases, Revit has supported the hiding of individual elements on a view-specific basis. While great for designers, it did pose occasional challenges for developers. Now, the API offers up:
Element.CanBeHidden ( View v )
Element.IsHidden( View v )
as well as:
View.Hide( Element e)
View.UnHide( Element e)
This should give developers powers similar to what you can do in Revit interactively (that fairness which every CAD developer yearns for :) ).
There are few enhancements with Family and FamilyInstance elements:
- Family.IsInPlace (this was possible heuristically in previous releases – but it’s always better to make it obvious)
- Family.IsCurtainPanelFamily (because of the special additional properties – it’s good to know this directly)
- FamilyInstance.IsSlantedColumn (another situation where there are special additional properties)
- FamilyInstance.Space (similar to familyInstances knowing which Room they reside in, now they know which space they reside in – very useful for MEP families!)
New Element Classes
The following classes are new in 2010:
- AreaScheme (see below)
- DividedSurface (with an amazing amount of depth!)
- Form (representing all of the Family solid content, and also with a huge amount of depth)
- ImportInstance (used for DWG imports, etc)
- PointOnEdgeEdgeIntersection (I think you might need to have a PhD or be Russian to understand this :) ).
- SpacingRule (structure and grids)
- TopographySurface (with an “AddPoints” method, no less)
There appear to be a few enhancements to Area elements that are of note:
- New AreaScheme element (this typically is set for “Rentable”, “Gross” but also apparently has some new BOMA settings for facilities management people)
- Areas have a link to their scheme
- ViewPlans have a link to the AreaScheme (where appropriate)
Dimensions also seem to have some upgrades in 2010. In particular:
- Dimensions have DimensionSegments
- The “Locked” property (read/write) has been added
Other Miscellaneous Enhancements
A few others that I couldn’t categorize:
- Blends now have access to Profiles, Offsets and VertexConnections.
- CurtainGridLines now have ExistingSegmentCurves
- Grid.ExtendToAllLevels method
- GBXMLParamElement now has an ExportComplexity object associated with it which contains all sorts of things to control how GBXML is exported (including, for example, how to handle Shading Surfaces).
- ModelCurve now exposes:
- Opening exposes IsTransparentIn3D and IsTransparentInElevation.
Two that I’ll be writing about a little later:
- Room.IsPointInRoom (XYZ)
- Space.IsPointInSpace( XYZ )
A few items seem targeted at making it easier to get geometry references and planes:
- Level now exposes a PlaneReference (to make things easier)
- SketchPlane exposes:
Wow. Again – there’s enough in these enhancements, new classes and more to keep us busy for quite some time.
(Part of the What’s New in the Revit 2010 API series)
For some people, the measure of a CAD API is always how many different types of elements it can create. Revit got off to a slow start in this category, but it continues to get stronger.
In this release, the new Revit API capabilities seem divided into:
- A significant amount of new MEP element creation
- A little bit of new Structure / Rebar options
- A significant amount of new capabilities around family content creation.
- A few very interesting things around the new freeform geometry and divided surface modeling in Revit 2010.
All in all, Revit can now create 70-100 different types of elements (depending on how you count the family content-related things).
What’s New for MEP Creation?
Here are the new MEP-oriented creation capabilities:
- Cross Fitting
(not being very MEP-savvy myself, I can’t add any real commentary to them other than to say it looks like an impressive list).
What’s New in Family Content Creation?
This whole area is new and exciting…
- Solid Forms
- Form By Cap
- Form By ThickenSingleSurface
- Supporting Elements
- Angular Dimension
- ArcLength Dimension
- Linear Dimension
- Radial Dimension
- Symbolic Curve
- Alignment (this looks interesting)
- Vertex Index Pair (this is a construct which defines how different profiles in a blend link together, I believe)
- Family Symbol Profile
- More Elements
- Model Text
- Freeform Modeling / Surfacing
- Curve By Points
- Divided Surface
- Reference Point
A Brief Story on Reference Points
A year or so ago I pinged Emile Kfouri, the Revit Platform Product Manager about why there were no “Points” in Revit (I can’t recall why I needed them – but I do know how old-time CAD people’s heads look like they’re going to explode when I say that they don’t exist). He said “Points are not BIM” – and I came to agree with the statement, in general (not that Lines are BIM – and they were prevalent in Revit still). In any case – while they’re not BIM, they are quite handy for building things – and it’s nice to see them in there.
A Few More…
Finally, there are a couple last additions and changes…
- Rebars defined by RebarShapes
- Hermite Splines (these are one of the building blocks of the new freeform modeling capabilities)
- Plane from Curves
- Topography Surface (Now this looks very interesting – just pass in an array of XYZ points and get back a surface? I haven’t had a chance to try it out yet – but it should be cool!)
Image: a spline-controlled surface with control points that can be dragged/modified.
All in all, this release presents a great deal of new capabilities around Element creation… certainly enough to keep most of us busy for the next year until Revit 2011 comes out!
Thursday, February 19, 2009
- RibbonPanel - creating an "area" to contain your application
- Pushbutton - a single Pushbutton command
- PulldownButton - a button which drops down a list of commands
- Separator - basic separation
Both Pushbuttons and PulldownButtons can have large (32x32) icons and small (16x16) icons (not shown above). The large icon is always displayed on the button, while the small icon is only shown if the user adds the button to the "Quick Access Toolbar" - which is always available.
Autodesk also released a 29-page document describing how icons should be created to fit in with Revit (who knew it could be so complicated? :) ).
The existing APIs that applications use to create both top-level menus or toolbars have disappeared - so you MUST migrate to this approach.
While I think that it's great that the Ribbon has come to Revit - I really like it... The UI straightjacket that we've been put in with the UI is a little tight... It would be nice if we could at least do stacked buttons like the rest of Revit.
(Editors Note: Stacked buttons, 2 or 3 high - was added in the API after this was written)
It's also a little unfortunate that everything external is confined to the "AddIns" tab - both because we used to be able to have "top-level" menus, but also because if you have a lot of applications loaded, the real-estate may get crowded.
(Part of the What's New in Revit 2010 API series)
Probably the biggest single improvement to the Revit API in 2010 is a wide variety of enhancements to supporting Revit Families - and it's been a long time coming.
Until now, the support for families has been spotty - for example, you could open family files as documents - but you couldn't see the types inside them - or really do anything with them.
Autodesk has implemented a dizzying amount of capabilities to help with:
- Analyzing Families
- Creating new Families (geometry, parametrics and all!)
- Reading and Writing Family Types, parameters, and even formulas
- Ability to examine Families embedded in projects
- Read/Write Family Element Visibility
- Control the loading behavior of families
Enhanced Document class
The core concept of working with families in the Revit 2010 API is the improved "Document" class. The Document class still represents both Project and Family documents, but it has been enhanced with the following properties and methods:
- EditFamily( family) - similar to context-menu Edit Family command
- FamilyManager (provides access to the types, parameters, and formulas related to the family)
- OwnerFamily - to deal with nested family components
The Family Manager is able to do a wide variety of tasks, including full control of adding, removing and renaming types, adding and removing parameters, and setting values and formulas.Creating Solids
Creation of elements will be covered in more depth in another post - but suffice it to say there is an impressive list of things that you can programmatically create through the new APIs, including:
- Model Text
- and much more
Visibility SettingsFor those of you who are not familiar with content building, one of the most critical topics to "get right" when building content is the visibilty settings:
Each element in a family has visibility settings - both which levels of detail it appears in as well as whether it appears in different types of views. These options are critical to building good content. For example, if you have intricate details in your family, consider if they should only be shown in "Fine" detail views. Also, if you have 3D solid content, one alternative is to NOT show the 3D solid in Plan views - instead, you would use 2D linework in Plan View. These approaches can make a SUBSTANTIAL difference in the performance of Revit - particularly as your building model grows.
While there had been undocumented parameter access to this information before, the new FamilyElementVisibility class makes this information easy to access for each element in a family.
If you've ever written an application that loads families into a project, you may have run into the problem of what happens when the family already exists in the project (particularly if you're using shared families). While the "DialogBox" event controls used to give a poor-but-workable method to suppress Revit's pop-up dialog boxes, the new loading methods give far better control over what happens.
The new LoadFamily method signature:
Family = Document.LoadFamily( string path, IFamilyLoadOptions options );
Family = Document.LoadFamily( Document familyDocument, IFamilyLoadOptions options);
The IFamilyLoadOptions, as implemented by the RevitUIFamilyLoad class, give you events for family loading as well as specific behavior control for whether to update the family, and whether to override parameters.
What Can You Do With All This?
There are a variety of capabilities that these features open to you... First of all, I suspect that a variety of new content tools will become available to better manage your content. If you manage a great deal of content, and need to make large-scale changes to content, these features will make it happen.
It IS possible now to extract project families back to RFAs - as well as doing better comparisons than previously possible between "embedded" families and standalone families.
Another big step for Autodesk - they now allow you to use the API insert a DWG file into a family. This had previously been deliberately disabled.
Hypothetically speaking, this means that you could possibly crank out thousands of families based on existing DWGs. But before you consider doing this - let me be among the voices saying - DON'T. Our research indicates that families created using DWG files are fundamentally terrible - they are "heavy", "slow", and "dumb". Almost all firms using Revit have discovered this - and are systematically removing these families from their library. Doing content correctly would be a great other post - and the API now gives you the tools to do things right... Please try to do the right thing!
Wednesday, February 18, 2009
(Part of the What's New in Revit 2010 API series)
In this post, we'll cover a few quick topics about general changes to the Revit 2010 API.
.NET 3.5 and Visual Studio 2008 SP1
First, the 2010 release has a new platform requirement for developing Visual Studio solutions - .NET 3.5 for users and Visual Studio 2008 SP1 for developers. What does this mean? Several things:
- First, every user of Revit 2010 will have the .NET 3.5 Framework pre-installed, taking care of the pre-requisite issue.
- We can leverage the new technologies available in .NET 3.5, including: Windows Presentation Foundation (WPF) for new look-and-feel, Language Integrated Query (LINQ) for easy access to data from databases, XML or the Revit model.
- Potentially improved deployment options with .NET 3.5 SP1, which resolves some issues that made it difficult to put Revit Plugin DLLs in a centralized network location.
As a developer, I also appreciate the ability to take advantage of the newer features of Visual Studio, including the built-in Unit Testing framework and language features like the new "var" keyword - where Visual Studio figures out variable types for you!
Compatibility with Previous Versions
The nature of the changes to the RevitAPI makes it likely that old applications will be broken in 2010, and will require re-compiling and some changes to make them work with 2010.
It is possible, if your ExternalCommand does not make use of any objects or properties that have changed, that the existing DLL will work - but I'd say that any ExternalCommand of any complexity is unlikely to work without changes.
We will talk about VSTA (Visual Studio Tools for Applications - Microsoft's replacement for VBA - Visual Basic for Applications) and Revit separately - but this version of Revit includes the 2.0 version of VSTA.
What's in a Name?
I've historically been curious about the directory that Revit gets installed in, i.e. "C:\Program Files\Revit Architecture 2009". It always seemed like Revit has held onto the "Revit" folder name while the other Autodesk products were all being standardized to be called "Autodesk _____".
So whether they just finally got around to it, or whether there's deeper intrigue - as of Beta 1, the product is now called "Autodesk Revit Architecture 2010", with the folder name to match.
Ok, this post was a little dry and boring - but I felt like these things had to be said up front... I promise it will get better from here :).
One of my favorite blog topics of the year is here - the "What's New" posts, describing the new capabilities of the API (application programming interface) for Revit.
In this series of posts, I'll try to lay out both what's new and what it might mean for you.
Since introducing a small .NET API in Revit 8, the API has doubled in size for each release. Obviously, that's not sustainable the bigger the API gets - and while I'm not sure of the "actual" size increase of the 2010 release, I can say that it's impressive in both size and thoughtfulness.
There is so much new, that we will break up the posts as follows
- General Changes in 2010
- User Interface
- Finally Families!
- Element Creation
- Element Enhancements
- Spatial Awareness
- Import and Export
- MEP Enhancements
- Geometry Enhancements
- What's Still Missing?
Whew! Even breaking it up into this many pieces, these are still going to be some large topics. I'd better get started.
Monday, January 26, 2009
It's sad - Jeremy Tammik has blogged more about me than I have this month.
(His latest is an outgrowth of an Autodesk Developer Network question I submitted a couple of weeks ago - about why, in the Revit API, asking for the "SiteAngle" dimesion format data causes an exception - along with a variety of other interest
The short version:
Revit will throw an Exception if:
- You are running one "vertical" (i.e. Revit Architecture) and you ask for a dimension type which is ONLY in another vertical (i.e. Revit MEP).
- You ask for one of the four unit types which are un-modifiable (i.e. SiteAngle, SheetLength, etc).
Not very friendly, but at least now you know :).
Thursday, January 22, 2009
I know, I know.... I need to post more...
Part of my excuse for not posting right now is that I'm writing posts that can't be released yet. I always enjoy posting about the new products (Autodesk 2010 products in this case) as soon as it's possible - but I think we're still at least a month and a half away from the "press-embargo" on posting.
I've worked with a variety of early versions - so I'm hopeful I'll have a bunch of stuff queued up to post in the March timeframe.
In the meantime, I'm going to start posting some of my content from the last Autodesk University, for those who couldn't make it.