Op 06/11/2019 om 11:15 schreef jr:
> hi,
> 
> Thomas de Groot <tho### [at] degrootorg> wrote:
>> Op 05/11/2019 om 01:19 schreef jr:
>>> "jr" <cre### [at] gmailcom> wrote:
>>>> ...
>>> 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
>>
>> 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"
> 
> pls read the added comments in the file.  the vars are only 'declare'd _if_
> there's any worthwhile "slack" to report.
> 
> the '#ifdef()' idiom though ought to work in any case (it does here).
> 
> 

Yes, I thought so. The problem is not with the macro but with my test 
scene. I shall try to add something there which bypasses this.

-- 
Thomas

Post a reply to this message