• This forum is the machine-generated translation of www.cad3d.it/forum1 - the Italian design community. Several terms are not translated correctly.

suppress the components and can not display them in tables

  • Thread starter Thread starter dicifa
  • Start date Start date
. So, guys, we're going to order.
ilogic is used to create automatisms of use by managing the bees of inventor with its programming language ,
more or less as it was done in the night of the times with the old autocad autolisp.
you can do (if you are able to..) even wonderful things!
the thing that is asked is to have practically the possibility to change to pleasure the content of a whole without changing it
the container, this also in real management becomes difficult; the alternatives could be, like, the use of the assemblies,
but here at the end we create different assemblies (and perhaps the game is not worth the candle ..) ; I find the macchinosi iassembly in their construction .. at the end perhaps I first mount several assemblies untied .. I lose however connection between them
which gives me the opportunity to replace a model with another, mind with ilogic I can also create a configuration
not already in the table. .
the other solution would be to take a shortcut (burnt to say, ethically incorrect .. but effective and simple. . )
ie go edit taroccando a manazza the table .. maybe putting an asterisk + a note somewhere to mò of reminder for future management ..
I know that sometimes you have to adapt to take shortcuts .. but in life there is worse ..sperando meanwhile
that our friends of portland perhaps implement some new possibilities!!

on this page :http://forums.autodesk.com/t5/inventor-ideastation/idb-p/v1232never go to read-write??

while as regards the difference between view rappr.ne and detail level,
the first manages visibility, colors, frames etc. so we can alleviate-appear the work of
video card with consequences on table 2d.
the level of detail works instead at the level of loading-downloading data in memory therefore has effects on management
of ram by suppression-replacements etc.
at the end both things serve as basic tools for the proper management of large assemblies (simplification etc.)
 
. So, guys, we're going to order.
ilogic is used to create automatisms of use by managing the bees of inventor with its programming language ,
more or less as it was done in the night of the times with the old autocad autolisp.
you can do (if you are able to..) even wonderful things!
the thing that is asked is to have practically the possibility to change to pleasure the content of a whole without changing it
the container, this also in real management becomes difficult; the alternatives could be, like, the use of the assemblies,
but here at the end we create different assemblies (and perhaps the game is not worth the candle ..) ; I find the macchinosi iassembly in their construction .. at the end perhaps I first mount several assemblies untied .. I lose however connection between them
which gives me the opportunity to replace a model with another, mind with ilogic I can also create a configuration
not already in the table. .
the other solution would be to take a shortcut (burnt to say, ethically incorrect .. but effective and simple. . )
ie go edit taroccando a manazza the table .. maybe putting an asterisk + a note somewhere to mò of reminder for future management ..
I know that sometimes you have to adapt to take shortcuts .. but in life there is worse ..sperando meanwhile
that our friends of portland perhaps implement some new possibilities!!

on this page :http://forums.autodesk.com/t5/inventor-ideastation/idb-p/v1232never go to read-write??

while as regards the difference between view rappr.ne and detail level,
the first manages visibility, colors, frames etc. so we can alleviate-appear the work of
video card with consequences on table 2d.
the level of detail works instead at the level of loading-downloading data in memory therefore has effects on management
of ram by suppression-replacements etc.
at the end both things serve as basic tools for the proper management of large assemblies (simplification etc.)
First of all, I thank you so much for your time, and your reasoning does not bend, but the fact remains that the isactive class should correspond to the suppression button and is abnormal that in a situation it behaves in a way (see ilogic brings the part to reference) and in the other no.
still thanks genesis
 
First of all, I thank you so much for your time, and your reasoning does not bend, but the fact remains that the isactive class should correspond to the suppression button and is abnormal that in a situation it behaves in a way (see ilogic brings the part to reference) and in the other no.
still thanks genesis
Anyway... ni, because isactive does not correspond directly to an isactive at the level of inventor bees (in the sense that there is not): If you want to do the same thing via vba you have to do:

mycomponentoccurrence.suppressed = true
mycomponentoccurrence.bomstructure= kreferencebomstructure

doing two "actions."

given the purpose of ilogic makes sense that the operations have been shortened: changing from normal to reference the distinct structure includes/excludes components from the table count and divides them into the bom, suppression/remotion suppression makes them see or not at the table (without charging them in memory, very useful in the case of complex assemblies)

at the end of the fair I see myself to overthrow the concept: it is a pity that the level of detail does not also store the distinct structure components! If this were the "game" to settle the quantities at the table would be easier. Is there a direct system?
a pity also that the components set to reference are not highlighted somehow in the browser.. .
 
Anyway... ni, because isactive does not correspond directly to an isactive at the level of inventor bees (in the sense that there is not): If you want to do the same thing via vba you have to do:

mycomponentoccurrence.suppressed = true
mycomponentoccurrence.bomstructure= kreferencebomstructure

doing two "actions."

given the purpose of ilogic makes sense that the operations have been shortened: changing from normal to reference the distinct structure includes/excludes components from the table count and divides them into the bom, suppression/remotion suppression makes them see or not at the table (without charging them in memory, very useful in the case of complex assemblies)

at the end of the fair I see myself to overthrow the concept: it is a pity that the level of detail does not also store the distinct structure components! If this were the "game" to settle the quantities at the table would be easier. Is there a direct system?
a pity also that the components set to reference are not highlighted somehow in the browser.. .
always clear and concise without turning around compliments you amaze me more and more. Anyway, I'm so cute as you are.
 
Yes, it would also take this option as an option (association of the suppression also wanting to separate) ..
Then it would be perfect!!
 
... at the end of the fair I see the concept to be overthrown: it is a pity that the level of detail does not also store the distinct structure components! If this were the "game" to settle the quantities at the table would be easier. Is there a direct system? ...
It is what we ask ourselves from the beginning, but at the moment it seems there is no solution.
 
someone with a little more familiarity with me with English make a good signal to developers
 
In reality inventor allows you to do what you want and is called iassembly. with the new releases it is easier to make them and in practice creates levels of detail where the components appear or not separate depending on whether or not they are in the relative member of an iassembly.
 
I'm sorry if I didn't answer you earlier, but the post is very old and I didn't remember the problem.
Now I've framed you, I've got an image that should make you understand.Cattura.webpIf you have specific questions, I'll try to help you.
 
I'm sorry if I didn't answer you earlier, but the post is very old and I didn't remember the problem.
Now I've framed you, I've got an image that should make you understand.View attachment 42881If you have specific questions, I'll try to help you.
thanks for the prompt answer, but the fact is that I just can't find the filters list, the windows that you put me in the picture how I can access it? Thank you.
for the moment I have clayed the problem using another method:
in the configuration of the axieme that I need I have selected all the hidden elements, properties, exclude from the distinct materials; in this way in the table once I go to make the distinction I will get the table with the only visible parts.
 
thanks for the prompt answer, but the fact is that I just can't find the filters list, the windows that you put me in the picture how I can access it? Thank you.
for the moment I have clayed the problem using another method:
in the configuration of the axieme that I need I have selected all the hidden elements, properties, exclude from the distinct materials; in this way in the table once I go to make the distinction I will get the table with the only visible parts.
I am pleased that you have solved, however just once you create the table in the idw file click on the edge of the table and arrive in the windows that I have attached to you
Say hi. .
 
Good morning to all, the problem of the suppressed elements that are displayed in the list parts at the table made me lose many hours of sleep, so I am happy to be able to communicate my solution, believing that the workflows proposed in this discussion are not able to solve the problem.
I have to do in my work with assemblies composed of numerous subsets that may exist or do not exist: the various configurations of the axieme I go to create them in a single level of detail using ilogic rules.
I consider creating a level of detail necessary to suppress components.
an example: in a beam I can have or not have an iron called 5.
through the ilogic rule

if esist_05=0 then
component.isactive("5:1") = false


component.isactive("5:1") = true

end if


control the suppression of iron 5

in the table list, if deleted, it does not appear! Why?

if the suppression of a component occurs by ilogic rule to this component is attributed the characteristic reference in the distinct components and this makes it invisible and not counted in the distinct and masses, volumes... .

if then the parameter esist05=1 (or true ) the condition of iron 5 returns to be normal and you see in list parts.
In this way inventor works and I think it is a perfect workflow!
just create the code to determine whether the component is suppressed or not.
do so many levels of detail for many different configurations in my opinion is only good if you are not interested in the accounting of the components of the axieme.
if configurations are many you should create many levels of detail. instead you can get the configurations in one level of detail by combining the user parameters values created by you.

if the suppression is carried out manually inventor does not consider reference the suppressed object, it is as if it were not visible, whether or not it matter what you thought you got!! all have defects.

create a level of detail and through ilogic formulas suppress the elements in order to get your configurations together, at the table will be ok.

Greetings to all inventors.

disability
 

Forum statistics

Threads
44,997
Messages
339,767
Members
4
Latest member
ibt

Members online

No members online now.
Back
Top