Op 05/11/2019 om 01:19 schreef jr:
> "jr" <cre### [at] gmailcom> wrote:
>> ... I wrote a macro which "scans" an object's BB ...
> 
> find attached the second update of the 'Bounder'.
> 
> things have changed a little.  now, if the object's BB is found to be "(near)
> optimal", the macro prints that and ends, otherwise, ie having some "slack", the
> macro prints the difference lines as before, plus the optimised extents and
> dimensions, as per Thomas's feedback.
> 
> also new, if "slack" is reported, two variables with the differences from the
> BB's min/max extents are declared, to allow use of the info from in-scene.
> after 'Bounder' has run, one can for instance:
> 
> #ifdef(Bounder_min_diff)
>    // do something
> #end
> 
> so.  version 3.  fingers crossed.
> 
> 
> enjoy, jr.
> 

With version 3, I get a parser error in the scene file when the object 
is considered as near optimal: "Expected 'numeric expression', 
undeclared 'Bounder_min_diff' found instead"

-- 
Thomas

Post a reply to this message