2022-06-01
01:14 AM
- last edited on
2022-10-03
04:26 PM
by
Oleksandra Vakariuk
This might be best explained through an example.
Imagine if you had a property that contained the embodied carbon of an element (kgCO²/kg).
Then you had an expression-based property that converted the kgCO²/kg to an RGB value.
Not sure exactly what that would look like, perhaps R = kgCO²/kg x 50, G = kgCO²/kg x 10, B = kgCO²/kg x 75.
Concat Expression R & G & B.
The end result would be a graphic override that could on the fly change the colour of an element based on its Embodied carbon.
At the moment you need as many GO rules as there is values.
Endless other applications
Hope that makes sense.
2022-06-01 09:18 AM
I would go even further than this. Elements should be able to have their properties set by reading other elements' properties. Combine that with expressions and you're in parametric haven 😉
2022-06-01 10:13 AM
One element properties belong to that element, I wouldn't expect further interaction with other element's properties on this level. But I would love to have the schedules overhauled into something with interactive expression functionality.
| Archicad 4.55 - 26
| HP Z840 | 2× E5-2643 v4 | 64 GB RAM | Quadro M5000 | Windows 10 Pro x64
| HP Z4 G4 | W-2245 | 64 GB RAM | RTX A4000 | Windows 11
2022-06-11 07:55 AM - edited 2022-06-11 07:56 AM
I want the ceiling in my secret torture chamber to always be at exactly 1.3m above the medieval torture rack. If I can read the properties of the torture rack then as I move it around the chamber and adjust it's hight to suit the heights of my variously vertically challanged henchmen, the ceiling will automatically move up or down to keep the overall depressive atmosphere of the chamber.
2022-07-08 05:07 PM
That's not the exact use case I had, but pretty similar. Muaahaahahaaa!