I was running down to town to have tea with my friend Otto on Saturday morning, and happened to see this autumn leaf lying on the ground. Turned back, picked it up, and made a picture of it in the sunshine on Otto's veranda. It is completely unretouched, I promise!
Back to the Revit API, here is a short note on another issue run into by Ishwar Nagwani, Technical Consultant in our Bangalore organisation, who recently contributed the pick points to create a new a floor sample, and answered by Harry Mattison of the Revit development team.
Question: I am trying to update an existing family parameter and set its value, but it is always throwing an InvalidOperationException saying "There is no current type". What is wrong?
Here is some minimal sample code to reproduce the issue. Only the family file name is hardcoded.
public class Command : IExternalCommand { public Result Execute( ExternalCommandData commandData, ref string message, ElementSet elements ) { UIApplication uiapp = commandData.Application; uiapp.OpenAndActivateDocument( "C:\\Projects\\FY12\\GE Revit\\SWBD-AV2.rfa" ); UIDocument uidoc = uiapp.ActiveUIDocument; Application app = uiapp.Application; Document doc = uidoc.Document; FamilyManager familyMgr = doc.FamilyManager; FamilyParameter param = familyMgr.get_Parameter( "Width" ); if( null == param ) { param = doc.FamilyManager.AddParameter( "Width", BuiltInParameterGroup.PG_GEOMETRY, ParameterType.Length, true ); } familyMgr.Set( param, 0.2 ); // set the value return Result.Succeeded; } }
Answer: The exception message actually says it all, albeit rather succinctly: "There is no current type".
FamilyManager.Set is used to set the value of a parameter for the current family type. The family you are working with had no types defined, therefore Set could not work. You can remedy this by adding a family type manually or with the following two lines:
if( doc.FamilyManager.Types.Size == 0 ) doc.FamilyManager.NewType( "Type 1" ); familyMgr.Set( param, 0.2 );
Again, thanks to Ishwar for sharing this!
Alexander, Александр Пекшев, points out another possibility below, saying:
You do not have to create a type! You can use the method SetValueString
instead of the Set
method – it does not require pre-creation of a type, and does what it needs – it sets the value for the parameter!