order of iteration For loop for FACE query

theodore_peters

I have seen the path method for getting the correct order of edges, is there a way i can do it for faces as well?

It creates the stairs, but as you know, it will not iterate thorugh the query in any specific order.

Any suggestions?

<div>&nbsp; &nbsp; &nbsp; &nbsp; var allfaces is Query = qEverything(EntityType.FACE);</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; var allfaces1 is Query = qCreatedBy(id + "mainsketch", EntityType.FACE);</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; var count =0;</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; var evallfaces = evaluateQuery(context, allfaces1);</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; for (var faces in evallfaces)</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; {</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; count+=1;</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; opExtrude(context, id + ("extrude1"~toString(count)), {</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "entities" : faces,</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "direction" : vector(0,0,1),</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "endBound" : BoundingType.BLIND,</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "endDepth" : count*definition.rise</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; });</div><br><div>&nbsp; &nbsp; &nbsp; &nbsp; }</div>

theodore_peters

I'm trying this method now, and it says qContainsPoint failed...any idea why?

        var beginningface is Query= qContainsPoint(qEverything(EntityType.FACE), vector(0,0,0));
        var nextface = beginningface;
        for (var i = 0; i < definition.staircount; i += 1)
        {
            var thisface is Query = nextface;
            opExtrude(context, id + ("extrude1"~toString(i)), {
                    "entities" : nextface,
                    "direction" : vector(0,0,1),
                    "endBound" : BoundingType.BLIND,
                    "endDepth" : (i+1)*definition.rise
            });
            nextface=qTangentConnectedFaces(thisface);
        }

theodore_peters

I got it!

        for (var i = 0; i < definition.staircount; i += 1)
        {
            var thisface is Query = qContainsPoint(qCreatedBy(id + "mainsketch", EntityType.FACE), vector(((i)*(definition.run/inch))+0.1,0,0)*inch);
            opExtrude(context, id + ("extrude1"~toString(i)), {
                    "entities" : thisface,
                    "direction" : vector(0,0,1),
                    "endBound" : BoundingType.BLIND,
                    "endDepth" : (i+1)*definition.rise
            });
        
           
        }

kevin_o_toole_1

I don't know the full code, but it's possible a cleaner way would have been to use a sketchEntityQuery, with the string id you used to originally create the entity. It would likely have slightly better performance, but mainly, it would avoid the code with manual calculation of that point for qContainsPoint (which could be hard to maintain as the feature evolves).

(Looking again, if you're finding sketch regions, those aren't associated with individual ids, so your solution is likely the best one)

theodore_peters

rather than offsetting by 0.1 i should use 0 and subtract the previous face from the returned query, i was getting tired and lazy at that point. I will update it.

theodore_peters

or instead of creating line segments inside the major floorplan, i could create a rectangle for each step and reference that ID with sketchEntityQuery

theodore_peters

FYI if anyone runs into the issue where it doesnt like the vector being used for qContainsPoint, it needs to be a length vector(multiply the vector by a unit)

the reverse is true for direction vectors, if your vector is a length vector make sure you divide by a unit