"Kenneth" <kdw### [at] gmailcom> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> >
> > Some features implemented in the normal parser never made it into the
> > functions parser.

I actually just ran across this last night - had to unravel quite a few things
to actually figure out what was wrong.

I think my first instinct might be to access the function via a macro, where the
macro first #local(ly) declares some variables
#local a = val.x;
and then uses those variables in a function call.

I ran into this while also grappling with the different interpretations of x, y,
and z (and u and v) in isosurface and parametric function blocks.  I will post a
request to clarify in another thread.

Post a reply to this message