Attribute not moving with the chained Point

[sunchuanpu]

Hello,

I used to do the similar thing on my old blocks, but it's not working for the new blocks I am trying to make this week. I cannot figure out why is this happening, thank you for your help in advance.

I give the attribute a chained point and move action to handle things like rotation.

As the sample drawing shows, when the upper left action move the chained point, the attribute does not move as I expected (but the chained point moves). On the other hand, when the rotate action move the point, both the attribute and chained point move correctly.

The fact that this Chained Point is only working "sometimes" really makes me confused.

[MMcCall402]

The Move action on point parameter Position 2, make a new selection set and select everything.

I guess a point/move doesn't chain to another point/move.

[sunchuanpu]

Including the attribute into the upper left Move action solve the problem, but doesn't solve my confusion, as doing this usually means double the "distance multiplier" in other cases.

Thank you for your response. I want to keep this question open and see if there will be anyone able to explain the reason behind this though.

[MMcCall402]

I re-open the original block, selected the Move action for the Position 2 parameter but this time when I made a new selection set I only chose the box and the two other parameters (Point and Rotate, for a total of 3 objects).   Then it operated as expected.  .... but why .... 

I rechecked the original selection set and saw that it was 4 objects.  The Base Point Parameter was the 4th object.  Including this in the selection is somehow messing up the chained point/move to a point/move.

[MMcCall402]

Adding another chained point/move parameter/action just to move the Base Point seems to work.  Doesn't make any sense but it works.

[h_s_walker]

@sunchuanpu It doesn't like having the point being affected by two different parameters. All I did was add the attribute to the move action.

See the attached drawing

[sunchuanpu]

Thank you for your response.

The intention was to have the Position1 (the Chained Point) also work as a grip to drag the label around, which means the point should be included in the upper left action's selection set.

MMcCall402 suggested a good solution to the issue, which is to exclude the base point from selection set, but I am still wondering the reason behind this and if I should avoid doing something in the future.