"jr" <cre### [at] gmailcom> wrote:
>
> > > [Kenneth wrote:]
> > > Would these be more appropriate for the docs' default?:
> > > target 1.0     When 'spacing' is used in the global photons block
> > > target on     When 'count' is used in the global photons block
>
> why 'on' ??
> (do you actually want to add further "ambiguities" to the parsing ?)

"jr" <cre### [at] gmailcom> wrote:
>
> > > Kenneth wrote:]
> > > Would these be more appropriate for the docs' default?:
> > > target 1.0     When 'spacing' is used in the global photons block
> > > target on     When 'count' is used in the global photons block
>
> why 'on' ??
> (do you actually want to add further "ambiguities" to the parsing ?

Sorry to say that I did not do much testing of 'target' behavior until now-- and
it is also a bit confusing to me.

Given that the docs say that the default for an object is 'target 1.0'-- which
should mean ON as I understand it (when *either* 'count' or 'spacing' is used in
the global photons block, both of which I tested) -- here are my current
parse/render results in both 3.7 and 3.8 beta 1. I used my test code posted
earlier.

photons{} -- an empty photon block-- the default for 'target' is actually OFF,
not ON.

With NO photons block in an object, the default is likewise OFF, not ON.

photons{target} -- neither 1.0 nor ON explicitly stated-- the object *is* a
photon target, as expected from the explicit use of the keyword

photons{target 1.0} or photons{target on} -- likewise ON as expected.

So it seems that the target default is OFF for an object-- unless I am
completely mistaken as the what 'default of target 1.0' means in the docs (other
than as an explicit 'spacing divisor').

Post a reply to this message