Why do iPart children exist?

[Anonymous]

What is the purpose of iPart Children? It seems to be redundant information
to me. All an assembly needs to know to re-create an iPart is the path to
the iPart parent/factory, and then the few parameters that define which
configuration to use. Why is this not just stored in the assembly file?

A quick glance at some of my children and I see that a stored iPart child is
even larger in size than the parent!

I must be missing something conceptually here...

- Joe

[Anonymous]

It's all about speed. If the part is already created and saved to the HD then IV doesn't have to recalculate each iPart child when you load an assy the child is used in. If the info was stored in the assy file then the assy file would be larger and would be slower to load in upper level assys.



At least that's my take on it.



MechMan

[Anonymous]

Can you imagine opening a large assembly and waiting for it to create all the iPart
children in some temp directory? Assembly files contain no parts... just like a MDT file
where everything was xrefed (instanced) in.

--
Kent
Assistant Moderator
Autodesk Discussion Forum Moderator Program


"Joe Dupre" wrote in message
news:4066F11E871964F59D1E98866B53C9C1@in.WebX.maYIadrTaRb...
> What is the purpose of iPart Children? It seems to be redundant information
> to me. All an assembly needs to know to re-create an iPart is the path to
> the iPart parent/factory, and then the few parameters that define which
> configuration to use. Why is this not just stored in the assembly file?
>
> A quick glance at some of my children and I see that a stored iPart child is
> even larger in size than the parent!
>
> I must be missing something conceptually here...
>
> - Joe
>
>

[Anonymous]

ditto to Kent and Mech's answers

--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
www.sdotson.com/faq.html
-----------------------------------------------------------------------
"Kent Keller" wrote in message
news:634D690131165820F7606B80CD815796@in.WebX.maYIadrTaRb...
> Can you imagine opening a large assembly and waiting for it to create all
the iPart
> children in some temp directory? Assembly files contain no parts... just
like a MDT file
> where everything was xrefed (instanced) in.
>
> --
> Kent
> Assistant Moderator
> Autodesk Discussion Forum Moderator Program
>
>
> "Joe Dupre" wrote in message
> news:4066F11E871964F59D1E98866B53C9C1@in.WebX.maYIadrTaRb...
> > What is the purpose of iPart Children? It seems to be redundant
information
> > to me. All an assembly needs to know to re-create an iPart is the path
to
> > the iPart parent/factory, and then the few parameters that define which
> > configuration to use. Why is this not just stored in the assembly file?
> >
> > A quick glance at some of my children and I see that a stored iPart
child is
> > even larger in size than the parent!
> >
> > I must be missing something conceptually here...
> >
> > - Joe
> >
> >
>
>

[Anonymous]

Double Ditto.

And... if you need to make modifications (drill a grease hole/lockhole in a
bolt or machine the head down or something crazy like this) to a "child",
you can open the child ipt, and savecopyas Step or SAT then use the Solids
Editing and/or regular feature tools to morph it.

QBZ

"Sean Dotson" wrote in message
news:0ACCC04AA4134C476DCB83ACC554F0E5@in.WebX.maYIadrTaRb...
> ditto to Kent and Mech's answers

[Anonymous]

I'll interject here just to say that I would like the ability to localize parts into an assy like MDT does if I wanted too. That's still an ability I miss from time to time.

MechMan

[Anonymous]

yuck!..(IMHO) and just when I was starting to like you...

--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
www.sdotson.com/faq.html
-----------------------------------------------------------------------
"MechMan" wrote in message news:f163cfa.4@WebX.maYIadrTaRb...
> I'll interject here just to say that I would like the ability to localize
parts into an assy like MDT does if I wanted too. That's still an ability I
miss from time to time.
>
> MechMan

[Anonymous]

LOL, I'm not saying you'd have to USE the option if you didn't want to. B-)

MechMan

[Anonymous]

One of the things I miss the most is the single file does all.

--
Kent
Assistant Moderator
Autodesk Discussion Forum Moderator Program


"MechMan" wrote in message news:f163cfa.6@WebX.maYIadrTaRb...
> LOL, I'm not saying you'd have to USE the option if you didn't want to. B-)
>
> MechMan

[Anonymous]

The single file loses it all as well. B-)


MechMan

[Anonymous]

Beat me too it...

Same reason I don't make multi sheet IDWs

--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
www.sdotson.com/faq.html
-----------------------------------------------------------------------
"MechMan" wrote in message news:f163cfa.8@WebX.maYIadrTaRb...
> The single file loses it all as well. B-)
>
> MechMan

[Anonymous]

"Beat me too it..."







B-)

MechMan

[Anonymous]

I can count the number of files I lost on less than one hand. 8^)

--
Kent
Assistant Moderator
Autodesk Discussion Forum Moderator Program


"Sean Dotson" wrote in message
news:2E5A7B75764036DCD067D0F46D5949A6@in.WebX.maYIadrTaRb...
> Beat me too it...
>

[Anonymous]

We frequently just take child parts and use them as the base for a derived
part and then modify that. Then should you need to update the I-part you
get correct geometry in the final modified version also.

Greg Purviance


"Quinn Zander" wrote in message
news:A427F38D3491F41E4EB42887B701CCDD@in.WebX.maYIadrTaRb...
> Double Ditto.
>
> And... if you need to make modifications (drill a grease hole/lockhole in
a
> bolt or machine the head down or something crazy like this) to a "child",
> you can open the child ipt, and savecopyas Step or SAT then use the Solids
> Editing and/or regular feature tools to morph it.
>
> QBZ
>
> "Sean Dotson" wrote in message
> news:0ACCC04AA4134C476DCB83ACC554F0E5@in.WebX.maYIadrTaRb...
> > ditto to Kent and Mech's answers
>
>

[Anonymous]

That's a trick I hadn't thought of. Thanks for mentioning it.

MechMan

[Anonymous]

Because the parent iParts went to a drive-in in a 57 Buick Roadmaster?

(can't believe no one else went there)

--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
www.sdotson.com/faq.html
----------------------------------------------------------------------------
------
"Joe Dupre" wrote in message
news:4066F11E871964F59D1E98866B53C9C1@in.WebX.maYIadrTaRb...
> What is the purpose of iPart Children? It seems to be redundant
information
> to me. All an assembly needs to know to re-create an iPart is the path to
> the iPart parent/factory, and then the few parameters that define which
> configuration to use. Why is this not just stored in the assembly file?
>
> A quick glance at some of my children and I see that a stored iPart child
is
> even larger in size than the parent!
>
> I must be missing something conceptually here...
>
> - Joe
>
>

[Anonymous]

The new iPart information has to be stored somewhere, and to store it in the parent would make it, dare I say again in one day: a part with a family table. Wow that would be great to have....

[Anonymous]

While a valid idea...as discussed before, it would take longer to load an
assembly with the info kept in the parent. It would have to iterate and
create the child every time. With IV's current method of loading files this
would take far too long.

--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
www.sdotson.com/faq.html
-----------------------------------------------------------------------
"boilerchip" wrote in message
news:f163cfa.15@WebX.maYIadrTaRb...
> The new iPart information has to be stored somewhere, and to store it in
the parent would make it, dare I say again in one day: a part with a family
table. Wow that would be great to have....