filtro show/noshow

[telemako71]

Good morning
first of all thank you for the useful advice that in the years have helped me.
I am a thermoplastic mold designer and my problem and I would like to know if you can create something to show some entities and noshow all the other... I tried using the display filters and partly it works ..the problem and that on some projects tells me that the number of entities to manage and too high and does not create the filter.

the fact and that often and willingly I have to change molds made by others...I would like to freeze entities in show with a filter just open the product so that after I made the changes of the case I can recall all the useful entities in show and send all the other in noshows.

thanks in advance for the answers
Daniele

 

[gianni55]

Hi.

but within a part or within a product?

inside a part, if you have so many solids and geometric groups that confuse you: from the instrument window, select "only the current body" and will display only the active part on which you are working, or as you have already done, assign the layers and then apply the filter (number of entities too high: Maybe it can happen, if you select too many geometries, try to reduce them)

instead within a complex product, I usually open the part on which I work in a new window, I only modify the part and then verify what happens in the product... if the monitor is large, you can open the 2 windows, and see live modification on the part and product.. .

if instead in a product you want to see some parts and others not, you create products "to lose" that in the end you delete only what you need:

e.g.

01) creo product 01
02) insert mold product
03) punch cup (of the mold product) in product 01
04) copy matrix (of the mold product) in product 01
05) ... and continuous for those who serve (of the mold product)
06) hid product 01 (so I have no confusion)
07) Modify punch and matrix (which also change in mold product)
08) when I have finished except the parts I have modified and I can also omit to save the product 01

In short, you create service products, where you separate the parts you want to see and those not, paying attention to keeping the original product without touching it or changing only the parts.

Let me know.

 

[telemako71]

thanks for the suggestion gianni55.

in most cases a product (although sometimes I find a part with 1000 body but in that case they are all on show the peeling and more than anything else to identify them and rename them)

I understand what you mean, I'll try because I don't see an alternative. . I was hoping there was a way to make a "photo" of all show/noshow entities to be able to return to the initial state to the temine of the change.....I don't understand how programmers have thought of managing thousands of entities thinking only to tell the end user click on one at the vote and tell him if you want to see it or not.

Does anyone know if you can make a macro that saves the show/noshow status of each entity and then reapply the display status when necessary?

 

[gianni55]

I think the problem arises from the fact that at first you have a product with noshow parts...

personal opinion: when a product is issued, everything must be visible as it is open/used/visualized by multiple users who do not need to know/interpret what should be displayed and what not (different address for parts and their constructions)

If someone requires it, I try to manage it with byproducts or in case I have to make exemplifying presentations I manage with scenarios, not to touch the main product.

in case there are thousands of parts, I use the "selection" mode that allows options such as: inversion, children, other or all (this to avoid sliding the whole tree looking for what is hidden and selecting one by one), so without freaking out everything visible

if you do not work on the product (add/toile details, bind etc.) but only on the parts, you could save a specific product with the parts you want in noshow and when you finished reloading them from the original product.

Let me know.

 

[falonef]

you could try with scenes or scenario function (excuse me but in Italian I miss the exact name)
I suggest you consider this function.
other possibility is to use ctrl+f that will allow you to search and select components by name or colors (but here you should make changes in advance)

we have developed a tool that allows us to easily and individually hide or display various elements (plan points sketches constraints etc) through a simple key

available

 

[telemako71]

personal opinion: when a product is issued, everything must be visible as it is open/used/visualized by multiple users who do not need to know/interpret what should be displayed and what not (different address for parts and their constructions)

you in a perfect world would be so, but as we know the experience teaches that things go differently.

you could try with scenes or scenario function (excuse me but in Italian I miss the exact name)
I suggest you consider this function.

Thanks falonef , I think it's the ideal solution , I did 2 quick tests this morning but I would say that it was just what I was looking for, when I showed the command scenes at the course associated with the management of the explosives and I assumed that it managed only the positions in the product .. instead it correctly manages the property show/noshow ... creating a scenario that fries the product at its opening I can return to the initial state of view click. :finger:

 

[falonef]

when you create the scenario you have 2 options: whole or partial.

depending on what you selected the result will be exactly what you want or the opposite.

 

[telemako71]

I tried it all and it seems to me to work. . .I went to see on the online guide but I didn't understand the difference ... I realized that with whole does a scan of all the product while with partial memorizes only the entities displayed .... Is there something I miss?

 

[falonef]

whole should be a scenario independent from the basic catproduct
partial instead is connected with catproduct > if you change the properties den catproduct, will have an impact also on the scenario

 

[telemako71]

thanks falonef

I did some tests and from what I understood a scenario can handle 4 attributes:

position (position)
hide-show (hiding-view)
graphic (graphic)
node activation (node activation)

a complete scenario (full scenes) stores the status of all 4 attributes and will bring back the component/product to that configuration. so if you still have to move something is not ideal because it will bring back the various components/products to the location where they were when you made the scenario.

a partial scenario (scene partial) allows you to choose which attributes to control on each component/product by differentiating the choices according to the needs... Maybe a component/product except location and display and another all 4.

I did not understand what the viewpoint needs but it does not seem essential at this moment :wink:

If I understand how the scenario works, it responds in part to my need because it acts on the components/products of a assembled but not on the parts or body that compose it.... in practice if I put in hide a body the scenery does not bring me back in show because it acts only on the state of the component. . So I'm guessing it's a good help, but it's not the final solution I was looking for:frown:

 

[gianni55]

If I don't remember badly, viewpoint stores orientation, location, zoom size etc., useful function when you have generated an explosion and returning to the scenario you want to reposition yourself exactly as you created it without placing yourself at attempts.

in fact the show/no show of the parts/components of the product has its own management of the properties (in assembly environment) other than that of a part (in part design environment) so if you want to act on the body, the speech changes, maybe you should act with a custom filter (from ctrl + f you create an advanced or preferred filter) but this involves the assignment of an associative parameter: name, color, lager, etc.

but do you have to return to the initial show/no show status or do you just have to make comparisons?

Maybe if you bring some practical examples you can find a strategy.

 

[falonef]

viewpoint allows you to orientate and save in the scenario a view to your liking

 

[falonef]

Can you give us an example of what you want?

 

[telemako71]

but do you have to return to the initial show/no show status or do you just have to make comparisons?

you just want to go back to the show/no initial state to avoid forgetting operational pieces in noshow or worse leave obsolete pieces on show

Sorry, but I didn't see that there was page 2 and I only realized now some vs. answers.

tomorrow I make a couple of pictures so I hope to explain better

 

[telemako71]

I put a very small part of the mold but the idea and this
I want that at the end of my operations what was on show see and what was in hide disappears regardless of what I activated or disabled to be able to work comfortably.

for example "sc01 translated" must be hide while "sc01" must be show

here is only one component the thing in the mold is repeated for another 100-200 components, so I would like something that sets itself automatically and not something that I have to do on every entity of my product (both it is another product and a single line)

I hope I've explained better

 

[falonef]

If I understood correctly, you would like to make visible what you had at first manually hidden and vice versa. but you don't know what you had hidden or displayed.

I recommend:
1. use scenarios to document pre/post changes (it would be a small aid)
2. use layers > the components you want to hide put them on a specific layer to deactivate
3. apply a color > what you hide, for example body, auxiliary elements etc. mark them with a color for example yellow. will be easier to recognize them and make them visible again
4. use of prefixes or suffixes > what you hide, for example body, auxiliary elements etc. marked with a prefix in the name for example: no-show_sc01 translated

I know very well that it will be a little laborious operations but at the moment I don't think of any other ideas.

Let us know

 

[gianni55]

I see it hard...

just not to throw the sponge, I would use the layers, but instead with the display filter, with the function find:

01) open the product (in design mode)
02) change/trova/advanced/attributed/visibility/=visible
03) binoculars and selects
04) from graphic property check layer 01/ send (for visible entities)

06) change/trova/advanced/attributed/visibility/=hidden
07) binoculars and selects
08) from graphic property check layer 02/ send (for hidden entities)

I work the changes when I'm done:

09) change/trova/advanced/attributed/layer/01
10) binoculars and selects
11) hide and display (2 times due to heterogeneous selection)

12) change/trova/advanced/attributed/layer/02
13) binoculars and selects
14) hide and display (2 times due to heterogeneous selection)

is however a system not recommended as:

for geometric groups and contained entities could work, provided that during the change you do not generate an entity you want is visible inside a geometric parent group that you assigned layer 02 (which will hide)

for bodywork works badly, since the body takes only one layer for all features, which consequently are hidden all, so when you want to view it by selecting it from the tree, the gear will be visible, but the features no...

if you can't assign layers or act on display due to too large selection, proceed to block using the current selection function instead of anywhere

Let me know.

 

[falonef]

other possibility:
- make sure you open the logical tree to your liking. 1.2.3 etc
- select the logical tree axcicella in order to activate it
- move the mouse in a libeto space and with the right click press selections

at the end you will have a pdf with all the elements. from their symbol you will know what the state was before the changes

 

[telemako71]

thanks to all and excuse the delay in the answer but at work they are really in the curves and I made some evidence only today.

color tips and prefixes are valid but the problem and I have to manage files made by external companies (and I can't impose on them to work with my rules) or archived months/years before by other designers (make me change names and colors of a file with thousands of features would become too long and dispersed for a few hours change)

I tried with the layers but in fact you do not manage the body for the reasons mentioned above

the image and too dispersive I should do too many prints and it would be a work of Carthonians.... otre that subject to human errors

I would say that the best solution and the combo "research+set selection"

01) open the product (in design mode)

02) change/modify groups selection/create group --> call it "visible"
03) without exiting the command "change selection groups"
04) change/trova/advanced/attributed/visibility/=visible
05) binoculars and selects
06) ok on the window "change selection group"

07) change/modify groups selection/create group --> call it "hidden"
08) without exiting the command "change selection groups"
09) change/trova/advanced/attributed/visibility/=hidden
10) binoculars and selects
11) ok on the window "change selection group"

I work the changes when I'm done:

12) change/selection groups/selection
13) hide and display (2 times due to heterogeneous selection)

14) selection/groups/hidden/selection
15) hide and display (2 times due to heterogeneous selection)

so it seems to me that it works I have to try to work with a decent file... at most I make more selection groups if the system does not manage them all in a blow

What do you think? Do you see any contraindications that escape a nabbus like me?

Daniele