http://www.charlesandhudson.com/archives/hand-tools-list-important.jpgPPT_LOGO_4b
‹#›
Autodesk Developer Network, April 2010
The Rice – Set Regeneration Option
•Registered Commands and Applications must explicitly set a Regeneration Option
•
•RegenerationOption.Automatic:
§The API framework will regenerate after every model level change (equivalent behavior with Revit 2010 and earlier). This mode is provided for behavioral equivalence with Revit 2010 and earlier; it is obsolete and will be removed in a future release.
•RegenerationOption.Manual:
§The API framework will not regenerate after every model level change. SuspendUpdating blocks are unnecessary and should not be used. Regeneration may be triggered by your application.
•
C:\Documents and Settings\walmslk\Local Settings\Temporary Internet Files\Content.IE5\EARWAUQM\MPj04096740000[1].jpg
This particular enhancement is both a rice and wine. This is something that you have to do but also has a lot of benefits of doing the same. Some of the audience might be familiar with Suspend Updating feature which disables Revit from regenerating every time we initiate some action. That mode will be still in available in Revit 2011 but there is also a new feature now which manually sets the regeneration option so that you can decide on when you want Revit to regenerate. This will be part of an attribute of the new command registration mechanism we shall talk about soon. So this would help in deciding if you want Revit to regenerate every time on its own or you want to manually regenerate when you think is more appropriate. So moving forward, Suspend updating might be obsolete with focus now shifting to RegenerationOption.