dress

[marco.mestriner]

Bye to all,
a question.
How come in the views 2d sw drawings, the daughter views of the main (orthagonal, isometric and so on) do not keep the components off as in the main view? I have for example a set of assemblies, if in the main view I hide a couple of these in the derived views reappear and I have to hide them again manually.
Moreover, why do the isometric views not maintain the interruptions of the views from which they derive? (the piece is projected whole).

Hi.
Mar

 

[drake]

to the first question the answer is x that the hidden components are only related to a view. you have to give the configurations in the model that then recalls in the table setting avoiding hiding the components manually.
to the second I don't know how to answer it because I don't happen to use the views with interruptions, but try to do so much x try... first make projections and then try to insert breaks on the main and see if it asks you to generate them also to the daughters.

 

[MassiVonWeizen]

you have to give the configurations in the model that then recalls in the table setting avoiding hiding the components manually.

more correct do display states in this case

 

[marco.mestriner]

to the first question the answer is x that the hidden components are only related to a view. you have to give the configurations in the model that then recalls in the table setting avoiding hiding the components manually.
to the second I don't know how to answer it because I don't happen to use the views with interruptions, but try to do so much x try... first make projections and then try to insert breaks on the main and see if it asks you to generate them also to the daughters.

Thanks drake,
I suspected something like that.
but I don't understand one thing, I have assimilars composed of many elements, should I create n configurations for n components to display them individually and make them executive tables? I find it a little complex as a system... is there no other procedure?
Thank you.

 

[drake]

you also display states, you are right, but you have to start using the configurations first in my opinion as the display states find them a little less immediate. . .

 

[drake]

configurations can also be n, but this is not the way to put individual components on the table. the individual components, in fact, put them on the table directly charging them as a model in the views.
configurations or display states can be useful when there is the need to hide some components that you do not want to show in some view. the setting up of individual components is another thing. do internal tutorials to understand using sw...