There is a built in function that allows iPart children to be created in
library paths. (It's one of those things I just attribute to magic and
don't focus on too much )
As for "why use a proxy path". Basically you use a proxy path if you want
the children to be generated anywhere OTHER than in the same directory as
the factory. If you have your factories in x:\path\ipart factories and the
children to be generated in x:\path\ipart children you'll need a proxy
pointing to this second directory. It's also useful if you use ipart on a
per project basis as opposed to a global basis.
"All I can see is that a proxy path is not displayed in the Open or Save
dialog boxes."
Actually it the Beta it was but they took it out. I found it useful and
would like to see it put back in....
Did that explain it?
--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
http://www.sdotson.com/faq.html
-----------------------------------------
"DJSpaceMouse" wrote in message
news:CA917F79680842948455614DD9D8256C@in.WebX.maYIadrTaRb...
> I think I generally understand the concept of a proxy path (i.e., a path
> name that begins with an underscore), but I'm having difficulty
> understanding its benefit. All I can see is that a proxy path is not
> displayed in the Open or Save dialog boxes.
>
> Then I read about using them when iParts are used in a library. Ok, this
> made sense to me... keep the iPart factories in the read-only library, but
> locate the child iParts elsewhere, because the factory may have to create
> new children but can't because of the read-only nature of a library. So,
I
> put an iPart factory in a library location (it was the handle.ipt from the
> samples), and tried to insert it into an assembly. It was my assumption
> that it would not be able to create the child iPart because it's in a
> library, but it did! Now, I cannot CHANGE the iPart factory or its
> children, but I can create new ones at will, even though they're in a
> library.
>
> So what benefit is there to placing the iPart children in a proxy path
(like
> Sean Dotson's project file posted 12/11/2002, 7:58am)? Can someone please
> straighten this out for me?
>
>