|
 |
On 9/21/25 10:35, Kenneth wrote:
> I noticed that you use the 'intervals' keyword in your SOR objects. In the
> current official POV-ray syntax, that keyword is used only for media. In your
> yuqk fork, have you eliminated that keyword usage in your SDL media code, so
> that it only applies to an SOR shape now? Or has yuqk's media 'intervals' been
> changed to some other word, perhaps?
The 'intervals' keyword is still there for media{} in yuqk and so it's
added to the group of keywords with more than one meaning(*).
I was first going to add a new keyword called 'segments' for this new
functionality, but with the sor{} it's defining interior sub-regions
alongside the 'surface segments'(**).
I've got hooks in place to add this kind of functionality to the
lathe{}. There it might make more sense to use 'segments'. Unlike the
sor{}, the interior regions cannot be cleanly broken up. With the
lathe{}, the spline can fold back on itself - the inside is set by the
whole spline.
In any case, the keyword 'intervals', like the functionality it enables,
is at this point a v4.0 suggestion; something to play with. :-)
Bill P.
(*) - I have mostly been de-layering keyword meanings in yuqk.
Introducing ip_ and it_ prefixes for pattern/perturbation and turbulence
related keywords, respectively. This work fixes a number of bugs caused
by keyword context overlaps in our official POV-Ray code.
There is too already a smaller ii_ prefix set for input/internal image
keywords. I'm still thinking about other keyword prefix groupings like
is_ for internal shape keywords; il_ for internal light_source keywords;
ic_ for internal camera keywords; im_ for internal media keywords. We'll
see.
(**) Functionality which makes the sor{} more useful as a csg helper
function / shape. Functionality which opens up the ability to use on
curve points as effective control points in the middle of the sor{}
spline. Functionality which better enables two or more sor{} shapes to
create off y axis surfaces of revolution with well defined inside regions.
In short, I'm coming away from this look/update of the sor{} thinking
the it might be more useful than I originally thought!
Post a reply to this message
|
 |