I do not understand the concept, but I will try to imagine it...
Pauvres_honteux wrote: ↑Sun Feb 11, 2018 10:59 am
Hi, I guess this one is targeted at
abdullah wrote:ping
.
I'd like to propose a function to make
any element in sketcher manually and purposely publicly available outside of the sketcher.
Additionally it would be nice with a function to make a "public profile" out of anything one click on (in an ordered manner). This simplifies the work with skeletons and makes them more versatile.
I am not sure I understand all the implications. A sketch is as public as any other element. A line from one sketch can be linked via external geometry from another sketch.
Pauvres_honteux wrote: ↑Sun Feb 11, 2018 10:59 am
Example points) All center points in one sketch. One publish them as groups or as individuals. Then one can use the separate group(s) as basis for user defined hole patterns. Odd hole dimensions are manually linked to separate published points. The beauty in this is that one has only one sketch were all relations are easily defined with respect to each other, i.e. change in one place and update everything in one go. This will also be a super nice feature when using Assembly3 and positioning a few hundred screws and their washers and their nuts and.... Extra nice when your colleague changes some hole positions a few zilly-meter without telling you...
The element defining the center hole can be linked from another sketch, then you can define holes by using circles. I can imagine some functionality may be welcome to automate such an operation (for example, that clicking a shape already creates a new sketch with linked external geometry and circles for hole definitions). From a 3D point of view, a new PDN feature, for example, taking as input an array of circles defining the centers of a pattern could be created to enable this "user defined" pattern replication.
A sketch defines a 2D space, so using it for assembly positioning may lack one dimension in a general case. I generally tend to think that an assembly wb should be able to handle those situations when a hole changes (it changes position on a face or even the depth changes).
Pauvres_honteux wrote: ↑Sun Feb 11, 2018 10:59 am
Example profiles) A lot of relations between profiles is needed so the simplest way will be to have them in one sketch. One then just starts the profile function and serial-click along until satisfied. Repeat this till intended number of profiles are created. Now these profiles (open or closed) can be used for whatever one pleases outside the sketch. Probably most used for projecting into other sketches for various purposes. At work I usually use them for offsetting after I projected them and then start off from there.
This limits to 2D relations, as define by a single sketch. The case with the profiles, as I understand it, is what the PDN helix tool does, use a sketch defined profile in an operation. The profile may be defined based on a master sketch by importing external geometry (which brings me back to something I wanted to implement in the sketcher, i.e. that external geometry can be made defining a sketch or not by switching the "construction mode").
There is one major thing I do not quite understand. If a sketch defines a 2D space, what exactly does the publish function do in order to enable it to be projected into a 2D space again?
Pauvres_honteux wrote: ↑Sun Feb 11, 2018 10:59 am
I'd also like to have these "published" elements visible as separate entries in the tree. Selectable of course.
Edit = blue color
So now it seems to me that you want to have like datums (point, line, plane) controlled by a sketch. This you can do using the expression engine to map the placement of the datums to a sketch. Automation might be brought in, but it must be defined how.
It is not that I am dismissing your idea, I am trying to be critical so that you understand what I not understanding and better define what you are looking for, which should allow me to understand it. As far as I understand it, you are not asking for a sketcher functionality extension, but something that expands multiple WBs. Such an idea expanding multiple WBs has to be incredibly well defined before creation. Otherwise it is marked for failure. Think of how I replied and try to better define what you want.
