HaroldL said:
JST,
I like your idea of having a distance control on the fillet tool, but I don't know that I would call my method a "work around" it's just the way GD/Alibre works, or doesn't work. ......
BTW, Have you submitted an enhancement request to Support for a distance control for the fillet tool?
"Workaround" pretty much means a way to do indirectly what should be a direct function, or is expected to work a certain way, but actually either isn't present or works in some unexpected way. Or, of course, it can be a way to avoid a problem that occurs due to deficiencies in software etc. Your choice how to define it here.
I suppose my issue is that I would not expect the radius to extend BECAUSE THE *EDGE* DOES NOT. It's a question of what controls the fillet.... I would naturally expect the EDGE to control it, since that is what you select to run the fillet along. I would forget all about the "depth of fillet" idea IF the edge controlled the fillet. In reality, the fillet evidently MAY go anywhere that is "touched by" the fillet, as long as at least one surface is contiguous and tangent to the fillet.
I'm not clear on how the various items were all done in your example, but I do see at least one extrude cut, which obviously works.
My EXPECTATION is that if I cut a rectangular hole, and fillet ONE edge with no "propagation", ONLY that edge should fillet, and ONLY for the length of the edge.
When tried, It worked three times as expected. But it does not ALWAYS work that way, apparently, and there is no clear reason why there is a difference. Here I made holes in the piece in three different ways, and put tabs on them. ALL filleted correctly.
THEN I made one with a slight relief on it. THAT ONE FAILED DRAMATICALLY.
Why the difference?
The workaround is presumably to make the relief cut AFTER the tab and fillet are done. But that seems wrong to have to do.
I hear the issue of "that's just how it works". But of course, that has nothing to do with how people work, or want to work..... if SWX, or perhaps several other popular programs work a certain way, and GD requires a much different way, GD may be "wrong", even if the GD way is "better". Windows isn't really very good as an OS, at least historically, but it is dominant, and so everyone just uses it. If one wrote software that contravened all sorts of windows default standards for how the mouse and keyboard shortcuts work, etc, market success should not be expected.
As for submitting a request, I have given up doing any of that until I am on to V17 and full "Design". At the moment, anything I give GD will be dismissed, since I am running V16 on XP, which is not supported, but by my experience and many reports, works fine, and should have no reason why a weird thing like this would occur from that alone. This is only until I can resolve ways to handle some very expensive legacy software that I use regularly and MUST still exist when this machine goes to Win 7. The S/W is much more expensive to upgrade than GD, but GD is forcing the upgrade on me now.