At the moment and actually since it's introduction, param-o is lacking basic functionality. it is at most as noticed by other users as well a preview of what could have been.
I came across a post from a few years back where Graphisoft argues that only 0.2% of users make use of it. Instead of addressing the elephant in the room they seem to have decided to straight up throw it out the window...
It is hard to not notice that param-o was yet another tool incorporated to "make waves" instead of turning into something useful archicad is really lacking - parametric control or multiple potentially different entities - not to be understood as a per object parameter input.
what could be improved to make it a viable tool which more than 0.2% of users will use:
- multi-entity parametric logic. At the moment there is no direct way of creating relationships across different entities. This is a huge limitation
- Improve integration with the rest of Archicad tools. At the moment it lacks any dynamic integration of other Archicad tools.
- Allow more complex tasks to be performed. Add a scripting node/capability to it. At the moment it is lacking functionality to make it useful for experienced users while still feeling too complicated for entry-level users. It alos feels way more like the unborn baby of dynamo rather than other more user-friendly platforms/interfaces.
- Incorporating iterability. One of the most basic things to incorporate - the ability to iterate/loop
Link to previous discussion on the topic:
make Param-O coder-friendly - Graphisoft Community
Open