Question about aring usage in library


Question about aring usage in library
#1
I am (finally) working on supporting the aring primitive in LDView's primitive substitution, and I have run into what I feel is a problem. The problem is that I believe that the aring can be used in two different ways:

  1. To fill in the gap between a standard-resolution curved primitive and a 48-resolution curved primitive
  2. To fill in the gap between 16-sided geometric curve and a 48-resolution curved primitive

I know that it is being used in situations that match option 1 above. I don't know if it is being used for option 2 or not. One (relatively minor) problem is that option 1 is incompatible with how LDView does primitive substitution when the curve quality is set to certain settings. I should be able to fix this. But there is no way for me to generate the primitive in a way that is compatible with both option 1 and option 2.

For option 1, the resolution of the inner part needs to track my primitive substitution curve quality, and the outer part needs to track the 48-resolution version of the same thing. When the quality is set to the default value, this would be 16 and 48. For the next notch on LDView's quality slider, the 16 becomes 24. Right now, the 48-resolution version remains 48 at that setting. (That would probably change. The next notch uses 32, and since 32 doesn't evenly divide into 48, that would have to change. Same for the next notch, which is 40. An easy solution is to use 64 and 80 for the 48-resolution version of those two notches.)

But if this primitive is used next to hard-coded 16-sided geometry, then the inner resolution would need to remain 16, no matter what the curve quality is set to. The current description for the aring primitive does specify that it interfaces between high-resolution primitives and normal-resolution primitives. So does this mean that interfacing with 16-segment geometry is not allowed? If so, I can make it work (although it will cause my primitive substitution to render more geometry for 48 curves when the curve quality is set to use 32 or 40 segment curves).

If it is used next to 16-segment geometry, then I feel that that needs to be forbidden, and a new primitive needs to be introduced to fill that (different) role.

Side note: for POV export, the first version of this primitive is no geometry at all. The second version is a chord.
Reply
RE: Question about aring usage in library
#2
Replying to myself: 18909.dat uses 16-segment geometry against the inside of aring primitives. It seems almost certain that other parts do the same, but I have not verified this. As far as I can tell, there are 113 official parts plus 48 official subparts that use aring primitives.
Reply
RE: Question about aring usage in library
#3
I have the feeling that aring should be deprecated, as I no longer use it in recent part. But maybe I'm wrong... Can someone show me an example where an aring should be used because there is no other solution?
Reply
RE: Question about aring usage in library
#4
(2 hours ago)Philippe Hurbain Wrote: I have the feeling that aring should be deprecated, as I no longer use it in recent part. But maybe I'm wrong... Can someone show me an example where an aring should be used because there is no other solution?

10288 seems to be a case of that
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)