Instance Param access in Shared, Nested Families?

[Anonymous]

Hello.

Is there a way to setup a nested Family to have its *instance* parameters
exposed for edit,
when the Parent Family is placed in a Project?

It seems that the Instance params are all disabled,
but I *can* access and edit the Type params in my nested Family.
(Tab-select on the Parent Family in a Project, to get to the nested Family
Properties....)

Can anyone offer some advice?

Thanks,
Corey

[Anonymous]

The instance parameters in the nested family become properties in the host
family. You need to tie the properties to an instance parameter in the host
family, which will become properties in the project it's used in.

Parameters become properties and properties become... nothing... so you need
to always link any properties to parameters for them to be accessible at the
next level.

"caLayton" wrote in message
news:6381160@discussion.autodesk.com...
> Hello.
>
> Is there a way to setup a nested Family to have its *instance* parameters
> exposed for edit,
> when the Parent Family is placed in a Project?
>
> It seems that the Instance params are all disabled,
> but I *can* access and edit the Type params in my nested Family.
> (Tab-select on the Parent Family in a Project, to get to the nested Family
> Properties....)
>
> Can anyone offer some advice?
>
> Thanks,
> Corey

[Anonymous]

"Matt Dillon" wrote in message
news:6381161@discussion.autodesk.com...
> you need
> to always link any properties to parameters for them to be accessible at
> the
> next level.

Thanks for the quick reply, Matt.

I'm still confused as to why the Type Parameters of the Nested Family are
exposed,
and the instance ones aren't?

I know how to link nested params through to a param in the parent,
but was exploring an alternate way to modify nested params/properties
without having to create a pram in the host just to control it.
Tab-select to isolate the nested component and change its instance property
values directly.
Maybe it can't be done?

There are times when the linked param method is the desirable one,
but in this particular case, I'd rather not "muck-up" the Parent with a
bunch of params that only exist to affect changes in *one* of the nested
families, if possible.

[Anonymous]

Likewise,
it sure would be nice to get a Nested Family's "flip" control exposed when
nested...

[rab_i]

I wonder this and I see good potential in being able to adjust instance parameters by tabbing and selecting each nested shared family to adjust their instance parameters. I wonder if this could be an idea to add features of how nested families can become more useful.

[martijn_pater]

---

@Anonymous wrote:
I'm still confused as to why the Type Parameters of the Nested Family are
exposed,
and the instance ones aren't?

Maybe it can't be done?

---

Some families are type-based only (ie profiles), you need to use type parameters and associate them in the type properties in the host family (ie. find the profile right click for type properties in project browser). You can associate instance parameters to those type parameters though.