no problem.
all of the door components are typical for every door we manufacture except for the mid-rail, which is optional. so, i created a linear parameter with a stretch action to adjust to the various sizes of mid-rails, and another linear parameter and stretch action to relocate the centerline of the mid-rail anywhere on the door. then i created a visibility parameter to allow me to turn the midrail and its editing grips on/off by selecting either 'midrail' or 'no midrail'
My dillema was when i create my door schedule, it was reading my linear parameter on the mid-rail for the size, regardless if it was visible or not.
so, i ended up creating a lookup parameter linked to the visibility parameter. i renamed the visibility parameter "midrail" for easy identification when running EATTEXT for the table.
in the lookup action's propery lookup table, i selected the input properties for the visibility parameter "mid-rail". i had to set 10 total input properties, because i have 5 different size mid-rails, so there had to be 5 listed as visible (midrail) and 5 listed as invisible (no midrail). then in the lookup properties, i just duplicated the value for the mid-rail size in each of the 5 properties listed as visible, and for the 5 listed as invisible i put 'NONE' for the lookup properties. and it actually worked...im so proud!
im loving all of this new stuff