Am 17.03.2016 um 01:31 schrieb jr:
> hi clipka,
> 
> On 16/03/2016 23:50, clipka wrote:
> 
> thanks for swift response.  this approach led to a different problem
> (see below).  the macro is stored in its own file and meant to be
> general purpose (to trace the outline of whichever object was passed via
> ObjId), and I need both the object's name (for feedback and to populate
> a field in the output), and the object to trace.  I'm now thinking,
> given the below, it might be easier/better to supply both the name and
> the identifier as separate arguments, do you concur?
> 
> jr.
> 
> 
> #declare Tobj = torus { ... };
> object { Tobj }
> mymacro("Tobj")
> 
> #debug concat("id: ", ObjId)
> 
> Parse_String(ObjId)
> #local bbox_min = min_extent(ObjId)
> 
> POV now fails on the min_extent since I'm passing it a string..

You need to use

#local bbox_min = min_extent( Parse_String(ObjId) );

But yes, it would probably be easier to have two separate parameters,
one specifying the object and one specifying a string to use as a "name"
for that object.

Post a reply to this message