jonasbits has quit [Quit: No Ping reply in 180 seconds.]
misterfish has joined #openscad
jonasbits has joined #openscad
ccox has quit [Remote host closed the connection]
ccox has joined #openscad
fling has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
fling has joined #openscad
anonymous has joined #openscad
<guso78>
Stupid question to the Gurus: openscad can Display objects very Well with and w/o edges displayed. Is it also able to display only selected edges, Corners, faces. Set IS defined by Algorithm. This would Help me to Debug my Algorithms
<teepee>
guso78: I don't understand what the question is. I did not have any coffee yet though
guso78_ has joined #openscad
<guso78_>
https://imgpile.com/i/9yGqti I am referring to the ability to highlight certain selected corners in addition to the regular 3D Display
<guso78_>
issue is: i am writing an algorithm which operates on 3D trianlges, which creates new points and it does not work yet. So i want to see a graphical representation my the problem to collect ideas how I can aid the algorithm to work
<J23k96>
guso78 you can display edges on a transparent colored object, or some kind of wireframe (which is not working)
<guso78_>
J23 i dont want to display all edges, but only selected edges, corners ...
<J23k96>
to highlight only one edge or vertex you need access to the points and some libraries have tools to show these
<J23k96>
i mean you need to tell which one you want to see
<guso78_>
Yeah, the information from what edges to see comes from my algorithm in cc code. its hard to pass this information to the openscad source code window. would be easier to pass it to a data structure. I start to realize that this does not exist(yet)
<J23k96>
if you build polyhedra you can use a module that shows just some points
<guso78_>
suppose that points[p] is a template and needs to be replaced by a cooridinate. rather than a sphere i thought about using a bottom-up triangle pyramid. it has less faces and even yields a pointing effect.
drkow has joined #openscad
<Scopeuk>
I think the idea is using the same points array you use for your polygon (indexed by the point you care about) positioning a sphere at that coordinate
drfff has quit [Ping timeout: 246 seconds]
mmu_man has joined #openscad
<guso78_>
yeah, but i dont have a polygon array in my SCAD code ...
<guso98>
@kintel, would would you generally support the idea to introduce the PolySetIndexed Object Type ?
guso70 has quit [Quit: Client closed]
kintel has joined #openscad
<kintel>
guso78 sure, but please sync with joseph_ as he's refactoring related code
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<guso98>
i dont see too much interaction as I am mainly working in the model generation/preparation and joseph_ is mainly working on displaying the generated data, but i might be wrong.
<guso98>
do you have any Intent on the name of the new Type, and mainly where to place the proposed getter/setter functions ?
misterfish has quit [Ping timeout: 240 seconds]
<guso98>
... and would you act as a mentor for performing this task ?
<joseph_>
guso98: Could what you want to accomplish with a PolySetIndexed instead be handled by collecting your desired subset of faces into another VBO and rendering it with a different color? That potential approach is the same kind of thing that kintel suggested as a way to show "marked" faces that result from a difference() operation.
fling has quit [Remote host closed the connection]
fling has joined #openscad
kintel has joined #openscad
<kintel>
Happy to mentor, but I'm going to be mostly offline until mid-august
<joseph_>
guso98: I just read the issue description (I was looking in PRs at first, which is why I didn't find it). Also I previously thought that PolySetIndexed was related to the problem you described earlier in the chat about highlighting certain faces/edges. So now I have a more general question, which is whether PolySetIndexed would have any different interface/usage than a regular PolySet?
<joseph_>
If I am understanding the proposal correctly, it might be the case that the desired indexing behavior could be achieved just with an in-place implementation change to PolySet. And switching between the two could possibly be handled with either an experimental Feature:: or a boolean parameter for the constructor like is_indexed=true/false
<teepee>
with inplace editing, I'm not sure a flag would be even needed.
<teepee>
but the separate implementation would greatly benefit a step-by-step transition
<teepee>
guso78: do you see any places that would require the current PolySet behavior? I would assume it could be fully replaced at some point