On 9/15/25 19:49, William F Pokorny wrote:
> The idea with both 'caps' and 'intervals' is to add inbuilt ways for the 
> sor{} to be broken apart and the pieces textured, used in CSG or for 
> debug and modeling.

An additional change with the sor{} for R20 of yuqk is to allow sor 
references to existing sor identifiers - while permitting changes to the 
caps, open and intervals keyword settings(*). In other words, today, if 
you want two sor shapes where the only difference is the open setting, 
you have to create two complete sor{} blocks including the point list 
and the 'open' keyword or not.

It is the case today that using sor { Sor00 } is no different than 
object { Sor00 } in that both allow only differing object modifiers 
within the braces after the sor identifier.

There is also no type checking the identifier reference matches the type 
of the block wrapper itself. While the debug compile of yuqk has already 
implemented some type checking for text{} and ???, R20 of yuqk will 
always verify the ID type for the updated sor{}. It must to enable the 
keyword settings of a referenced sor ID to later be modified.

Attached an image and the scene file used to create the four sub images.

Bill P.

(*) - I thought I had the code for this in hand a week ago, but nope. I 
believe I've now got a clean implementation...

Post a reply to this message

Attachments:
Download 'parsingchanges01.pov.txt' (4 KB) Download 'parsingchanges.png' (71 KB)

Preview of image 'parsingchanges.png'