![]() ![]() You have a code that creates an array A, and then later on code that does something to elements A, A and A - elements which you semantically understand as "frobnicators of A", and whose number and indices depend on the contents of the array. I'm also not sure if I understand the problem description correctly, but based on my little experience with 3DSMax, Blender and SolveSpace, I'd use this programming analogy: You could also force the user to mark and name objects in the sketch on which other sketches can depend - and when you edit the sketch you'd have to set them up correctly after the edit. I only every used Free Cad so I don't know how other CAD solves this problem, I can see using a better heuristic (like the least change of the plane and distance of the sketch ? ) or forcing the user to specify which edge corresponds to which when editing a sketch that isn't the final one in the dependency chain. You can decide basing on some heuristics, but that heuristics sucks in FreeCad and is almost never right. There's no face_2 anymore - new side faces of the cuboid_1b are each in different places and at different angles than side faces of the old cuboid_1. pocket the sketch_2b creating a round hole in the cuboid_1b but where exactly ? create sketch_2b (a round circle) in the middle of face_? pad the sketch_1b into a cuboid_1b (face_1b, face_2b. Then you change the sketch_1 making it a pentagon instead of a rectangle. pocket the sketch_2 creating a round hole in the cuboid_1 create sketch_2 (a round circle) in the middle of face_2 (which is on the right side of the cuboid) pad the sketch_1 into a cuboid_1 (face_1, face_2. The problem with CAD is - you don't know. You need to know which autogenerated names from the last generation correspond to which autogenerated names in the current generation. It can take a lot of time and effort (especially if it ends up diverging into multiple separate issues at step four), but honestly when any of this process results in an open source project fixing a bug or introducing a new feature as a result, the sense of reward is well worth it.Īll that said: I don't know if is the same issue, but it sounds similar and might appreciate your input :) * If you run into implementation issues (like the kernel-level concern), then GOTO 1 with the same escalation path for the design issue / dependency it relates to * If you're really motivated and have the time, digging into the source and attempting an implementation often educational even if not immediately resolvable * If you have a precise problem or feature in mind - which it sounds like you do in this case! - finding/creating a bug for it and/or just commenting with your interest can help projects prioritize it * If you're unsure about the project and/or community's stance on a feature/problem, sometimes their discussion forums can help Having spent more time working on open source tools and projects recently: although yes, many codebases have limitations, there's often a rewarding escalation path towards improving the situation. I hope to find an up to date video series I can follow to learn more as I'm sure it'll become a lot easier to use once I understand the tools better. On the other hand, I found creating drill holes, countersunk or counterbored incredibly easy and powerful. The bugs which cause parts to just disappear when you run certain operations are an issue, and there is little help to explain the cause, I've gotten a few designs into the broken state others have mentioned where you need to undo a bunch of work to recover, which is unfortunate. Sometimes you know what you need to do, but can't find the tool for it because you have no idea what it's called in CAD land. I have generally found it quite hard to achieve some simple designs, it's not always easy to understand what a tool does from its name, and it's not always easy to find a video online to help. ![]() I have no CAD experience outside of what I learned in university over a decade ago, so it has been a challenge. ![]() I started using FreeCAD recently after getting a 3D printer, because I wanted something open source and runs on Linux which I could learn, and would become my CAD tool. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |