Announcement

Collapse
No announcement yet.

Filter <Family Type> Drop-down menu in nested subcomponents

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Twiceroadsfool
    replied
    Door Frames. Easily 50. Door Panels. Any kind of Hardware Options. KeyPlan types (ive got 10 in my template now). I wouldnt dream of putting Yes/no's on all that stuff, when a simple FT and a naming strategy takes care of it. Just an opinion though.

    Leave a comment:


  • anthonyB
    replied
    Agree. But most of the time I find my options are only two, which I can handle with a Not statement. Or if there are a bunch I still use Yes/No and group them sensibly in the dialog. Our users can much more easily understand this than the cryptic options under the Family Type parameter option. Have not had to work with fifty options though.

    To me it is all about the communication and I like options to be displayed in front of me and not buried in an option button or a pulldown menu.
    Last edited by anthonyB; March 30, 2016, 09:18 PM.

    Leave a comment:


  • Twiceroadsfool
    replied
    That works when its one or two items. When its 50... Not so much.

    Leave a comment:


  • anthonyB
    replied
    I don't like the Family Type parameters for that very reason. I use Yes/No options instead.

    Leave a comment:


  • mendler
    replied
    Originally posted by GMcDowellJr View Post
    Blunder or not that's what we have to work with. I'd suggest using a naming convention that makes it as clear as can be which to use. If it breaks they'll know they did something wrong!

    Thanks yeah, I think I'll just put a prefix in CAPs for the subcomponents so they don't get confused.

    M

    Leave a comment:


  • GMcDowellJr
    replied
    Blunder or not that's what we have to work with. I'd suggest using a naming convention that makes it as clear as can be which to use. If it breaks they'll know they did something wrong!

    Leave a comment:


  • Filter <Family Type> Drop-down menu in nested subcomponents

    Hi,

    I have an annotation family which has two generic annotation families nested within it.

    In the parent family, I plan to have instance parameters attached to the type label of each nested family, so I can independently define the type of each subcomponent in the project environment.

    However, because the nested families are of the same category <Generic Annotations>, my two dropdown menus cross-reference eachother.

    This will lead to confusion because I want the instance parameter for one subcomponent to only refer to the available types within THAT family, not the other one, and vice versa.

    Is there a way to manage this or is this another factory blunder?


    Thanks in advance,

    M

Related Topics

Collapse

Working...
X