Totally agree, and further to this the ability to read profile related requests in the parameter/master script i.e...
n = REQUEST ("Name_of_Profile", index, name)
n = REQUEST ("Profile_default_geometry,..."
Currently there is a Profile parameter type which lets the user select a profile. This is great in 2D/3D where the geometry can be used in the modelling, however you cannot assign any requested information from the complex profile to a parameter for further calculation (unless the value is only used temporarily at run time).
Graphisoft, why are all of these requests given the
"Expression returns 0 and contains dummy return values (emtpy string or 0) if used in parameter script, causing additional warning."
treatment? It is insanely frustrating and severely limits possibilities!!!
AC21 (8002 AUS FULL) | AC24 (7000 AUS FULL)| Windows 10 Pro | Intel Core i7-12700 @ 2.1GHz | 32GB RAM | NVidia T1000