We used to create an Area parameter for FilledRegions and then use a script to write its Areas there. This way it's possible to create Schedules and create different sums. However, this workflow would require to constantly update these values manually. There is a way to create an EventTrigger(hook in pyRevit) to update them automatically, but I usually avoid them to make sure I don't slow don't the work with any EventTriggers. But might be worth sometimes.
@@ErikFrits i tried a dynamo script, but theres a issue when set parameters By name. - "Elements.SetParameterByNameTypeOrInstance operation failed. The best overloaded method match for "Revit.Elements.InternalUtilities.ElementUtils.SetParameterValue (Audoted.Revit.DB.parameter, Double)" has some invalid arguments." - i tried the new parameter has integer, text, number and area parameters type. Every try gives the same error. Any help?
I am not really a Dynamo users, so not sure what went wrong with your Nodes. You can check my video on Parameters to understand how to get and modify them using python. (Search for Revit API parameters, I am sure you will find it) Then you will be able to change parameter inside Python node in Dynamo. P.S. I teach Revit API for pyRevit and Dynamo has a few minor differences with the main ones: - how to get doc,uidoc - and make transactions I have a short video breaking down these differences as well (Dynamo vs pyRevit) Hope this helps. Happy Coding!
I think CPython means the regular python version. IronPython is a special build that has the ability to use .NET libraries with clr module. And since Revit is built on .NET it's necessary to access Revit API. CPython shouldn't have access to any .NET libraries by default, however I believe there is some sort of bridge in Dynamo that does something in the background to access it. If you look at IronPython and CPython syntax, you won't find any differences. IronPython for a long time was built on 2.7.18 version of python, so it didn't have newer features that latest version of python has. But recently it got updated to IronPython 3.4.4 (If I remember the version correctly). So regular python gets way more updates and a few new features, while IronPython is very rarely updated. Not sure why it's like this, but I also don't care about it as much. Overall, don't focus too much on the python version, as there are very minimal differences. At least that's how I deal with it ;) Happy Coding!
dude - these are amazing!! thankyou!
Thanks, Enjoy new tools ;)
Thanks
Thank you
My pleasure!
Amazing feature helpful while using filled region
Thanks!
Filled Regions are awesome 🙌
Greta options to work with Filled regions
Thanks Erik! Happy new Year
🎅Happy New Year!
🎁Enjoy new tools ;)
Very nice!
And it is possible to get a schedulle of filled regions areas?
We used to create an Area parameter for FilledRegions and then use a script to write its Areas there. This way it's possible to create Schedules and create different sums.
However, this workflow would require to constantly update these values manually. There is a way to create an EventTrigger(hook in pyRevit) to update them automatically, but I usually avoid them to make sure I don't slow don't the work with any EventTriggers.
But might be worth sometimes.
@@ErikFrits i tried a dynamo script, but theres a issue when set parameters By name. - "Elements.SetParameterByNameTypeOrInstance operation failed. The best overloaded method match for "Revit.Elements.InternalUtilities.ElementUtils.SetParameterValue (Audoted.Revit.DB.parameter, Double)" has some invalid arguments." - i tried the new parameter has integer, text, number and area parameters type. Every try gives the same error. Any help?
I am not really a Dynamo users, so not sure what went wrong with your Nodes.
You can check my video on Parameters to understand how to get and modify them using python. (Search for Revit API parameters, I am sure you will find it)
Then you will be able to change parameter inside Python node in Dynamo.
P.S. I teach Revit API for pyRevit and Dynamo has a few minor differences with the main ones:
- how to get doc,uidoc
- and make transactions
I have a short video breaking down these differences as well (Dynamo vs pyRevit)
Hope this helps.
Happy Coding!
@@ErikFrits thanks very much!
do you have a tool to colour elements based on elements types?
No, but I could make it.
Can you describe the workflow on how you want to select elements to color.
could be awesome to have possibility to cut filled region with multisegmented lines or cuvred line
A bit trickier, but I will see if I come back to it.
Lots of tools on To-Do list, but nearly no time right no 😔
Hi, Revit 2023 is working on Dynamo Cpython3 , Can you Explain iron python vs Cpython3. Thanks
I think CPython means the regular python version.
IronPython is a special build that has the ability to use .NET libraries with clr module. And since Revit is built on .NET it's necessary to access Revit API.
CPython shouldn't have access to any .NET libraries by default, however I believe there is some sort of bridge in Dynamo that does something in the background to access it.
If you look at IronPython and CPython syntax, you won't find any differences. IronPython for a long time was built on 2.7.18 version of python, so it didn't have newer features that latest version of python has. But recently it got updated to IronPython 3.4.4 (If I remember the version correctly).
So regular python gets way more updates and a few new features, while IronPython is very rarely updated. Not sure why it's like this, but I also don't care about it as much.
Overall, don't focus too much on the python version, as there are very minimal differences.
At least that's how I deal with it ;)
Happy Coding!