Double lookup with 2 action; stretch & visibility function

[Anonymous]

Hi Guys,

I'm new here and i would like to ask your assistance. I attached a wardrobe dynamic block whereas if you stretch into a certain distance it change the number of door leaf of the cabinet. It's like if the width is greater than 650 it becomes 2 door ("2D" visibility state) and if its less than it becomes single door ("1D" visibility state). Unfortunately, when i am trying to do the action in the other visibility state that i have created its always goes back to the last lookup action. For instance, "2LH" (visibility state: 2 door leaf with hanger), if i want to do the same what i have made to the previous one, every'time i stretch, the output is always the same. With this, i would like to ask our good fellows if there is any way, i could manage this.

Thanks in advance,

MK

[Libbya]

Basically you always want the door a single door in the lower range and a double door in the higher range?  You want the selection of hanger to remain unchanged when the door changes? 

If that is correct then you need to add a 'memory' parameter (point parameter works best) to store the hanger selection.  You then need visibility states with the single door with each hanger option and visibility states that have the double door with each hanger option.  You then have a single lookup move the 'memory' point based on the hanger selection.  The memory point and linear lengths go then go on one of the double lookup tables and they determine each of the possible rows that the visibility state is switched to using the second table.  

[Anonymous]

Hi Mr. Libbya,

Yes, you are correct, that's what i exactly want. However, it's a little confusing to me 'coz this is my first time to encounter a "memory parameter". Perhaps, if you could please show me an example, it will be helpful for me to follow. I'l be grateful for this.

Thank You very much,

MK

[Anonymous]

Hi Mr. Libbya,

That was awesome. I really appreciate what you've done, but if its not too much, may i have the edited file. You can email to me at rafcube@gmail.com or you can post here too...

Thank you very much,

MK

[Libbya]

I didn't save it.  When I make a screencast I never do.  I have no use for the block afterwards and I find that it is counterproductive to the learning process (what the forums are for) to do someone else's work for them.  You will end up understanding Dynamic Blocks better after following the step-by-step process.  If you get stuck, report back and I will try to assist further.

[Anonymous]

Hi Mr. Libbya,

Ok I understand. Once again, Im very thankful.

MK.

[Anonymous]

Hi Mr. Libbya,

Attached is the block that i have made through the help you gave me and i have been using it for a week and my question is, how can i set a default visibility on my look up because every time i insert the block, I always have to select first in order to run the blocks smoothly. Perhaps i missing something, would you please take a look.

Thank you very much,

MK.

[Libbya · Accepted solution]

You need to place the 'MEM' point parameter at the location within the block that corresponds to the topmost visibility state on the visibility list.

2D is the topmost visibility state.  If you look at the two tables of the double lookup you will see that the 2D visibility state corresponds to a value of 1 for MEM X and for a value within the range of [58'-4",100'] for W.  The as-drawn distance for W is 66'8 which is within that range.  The as-drawn value for MEM X (base X) is 0.  Change that to 1 and your block should work properly when inserted.  

[Anonymous]

awesome!!! I got it.

Thanks again for this....

Till next time..

[Anonymous]

Hi Mr Libbya,

What's the best way to do, to control the handle type and door type of this block.? Is it possible to create separate MEM parameter for each and then combined it (i tried but no luck) so that if i wish to add another type it will be easy to input and track. Do you have any suggestions and ideas to do this properly, because the more i add the more it become complex.

Thank you,

MK

[Libbya]

How many different visibility states are you wanting for the handle?  When do you want them to show?  You can use the MEM Y to store the value for the handle.  With each new visibility selection, the total number of visibility states required can grow very quickly and the block can indeed get quite complex.     

[Anonymous]

Hi Mr. Libbya,

Attached is a sample that i have made under "Door" visibility. Could you please have a look on it because i can't figure it out. The "Handle" selection doesn't retain'when ever i change the Door Type. Im sure i missing something ór perhaps my lookup are not properly done. 

Thank You,

MK

[Libbya]

If you want the handle selection separate from the other selections, then you need to store the handle value separately from the other selection values.  That is why in my last post I said to use MEM Y rather than MEM X.  You then add MEM Y to the double lookup table.  On the input table for rows where the handle is not shown, use the range of values fro MEM Y.  Use the specific value for rows where the handle is shown.  

[Anonymous]

Hi Mr. Libbya,

I try the things you have told me but some handle type and door type are freezing. I also change the MEM Y base location which help me run the block quite but still I can't figure it out. please help..

I attached the one that i made.

Thank You,

MK

[Libbya · Accepted solution]

You misunderstood what I said about the range value.  MEM Y has nothing to do with MEM X.  They are completely separate values.  When the handle selection does not matter for the current state you should have a range value that covers the range of MEM Y values that are used.  You use 90, 91, 92, 93, 94 for the handle selections.  When the handle does not matter, you can use any range that covers those values, e.g. [0,1000]. 

[Anonymous]

Hi Mr. Libbya,

Thanks again, i finally figure it out. It works perfectly. Just one question, is it possible to input a variables or expression inside the lookup? if its yes what's the format...

Thank you,

MK

[Libbya]

Nope, lookups will not accept formulas. 

[Anonymous]

Hi there,

I attached a door cabinet block where the handle is movable. I'm just wondering if there's a way in point parameter or in any to move the same object UP & DOWN in Y plane and move opposite direction in X plane. I made it in X direction but i can't figure it out in Y . I want only a single grip that will do both to minimize the selection, that's why I prefer a point parameter. Kindly have a look.

Thank You,

MK

[Libbya · Accepted solution]

Yes, an XY parameter gives a property to stretch/move actions that allows you to separate the X and Y components of the move/stretch and alter them using the distance multiplier or angle offset.  See screencast.