filletting all edges of an extrusion from a configurable side-count polygon sketch

kyle_altendorf

https://cad.onshape.com/documents/c33a129a265878827757e5d3/v/4c30a8fe33b0236c4dd82e9f/e/a1548ab63b4ab34eda0fdf40?renderMode=0&uiState=67c269a9de42422e65811b6f

I feel like I'm missing something in terms of configurable parts and doing operations that involve selecting a different number of items. Here I made a sketch using an inscribed polygon. The values configuration item controls the number of sides of the polygon. At the point of the link and screenshot I had set the values to 3, then edited the fillet to select the three edges. Then, I increased the values to 6. Interestingly, the fillet feature now creates 4 fillets. More than the 3 selected edges and less than the total edge count. I tried using Select → Parallel edges. It suffers the same failure as the parallel edges are identified at the time of selection, not the time of regeneration when there may then be a different number of edges. I think that way back on Pro/E I was able to select something like 'edges created by this extrusion'. I have already implemented some featurescript for something else to do something akin to this, I think. It just seems a bit much to have to reach to custom featurescript, then pass-through all the fillet options and…

Am I missing something? Or is this just not doable in a clean and simple way. This question is adjacent to the linked post below.

Thanks for any pointers. (and all the pointers in my other posts already)

Cheers,

-kyle

https://forum.onshape.com/discussion/26772/is-it-possible-to-create-custom-select-queries-for-use-in-the-gui

jelte_steur814

try @EvanReese's selection fillet feature:

https://cad.onshape.com/documents/1da236b5e61f1061327374d5/v/114d54563e4295fb48503215/e/327c207d9694c71a6c3a5c53

He's also made a youtube video on smart selections.

Coding up an 'auto fillet' custom featurescript that creates feature dependent fillets may be the fallback depending on how far you get with selection fillet.

kyle_altendorf

Thanks for the link and suggestions. I'll take a look. I've also done some of this by working on 360/#n sections and circular patterns. That can work as well but has it's own annoyances.

kyle_altendorf

I looked up the video and watched it. Some good suggestions in there. Thank! The end of the video is exactly what I was asking about here. I agree that while it is very valuable to have featurescript for so many things, it does not address the lack of a selection feature itself. Evan referred to the need for 'persistence' though the words in my head were 'delayed evaluation'. Either way, not having some implementation of this makes certain things much harder than they need to be. As another example I just hit, I would like to be able to use the entire set of wave surfaces to do a split. I created the selection when the part had three waves and then changed the configuration variable to instead be nine waves and now have only 1/3 of the top surface selected.

Anyways, as with all your help on most of my questions here, thank you @jelte_steur814 !

https://youtu.be/o9HyVenlLW0?t=702

kyle_altendorf

For the record, this is where I went for my second case. Minimal, good enough for the exact need just there.

FeatureScript 2599;
import(path : "onshape/std/common.fs", version : "2599.0");

annotation { "Feature Type Name" : "Tangent Face Split" }
export const tangentFaceSplitFeature = defineFeature(function(context is Context, id is Id, definition is map)
    precondition
    {
        annotation { "Name" : "Faces to split", "Filter" : EntityType.FACE }
        definition.targets is Query;

        annotation { "Name" : "Entities to split with", "Filter" : EntityType.FACE }
        definition.tools is Query;
    }
    {
        var tools = qTangentConnectedFaces(definition.tools);
        addDebugEntities(context, tools, DebugColor.CYAN);
        opSplitFace(context, id + "split", {
                "faceTargets" : definition.targets,
                "faceTools" : tools
        });
    }
);

kyle_altendorf

removed double post