Resetting or Editing Parameter Points for Actions?

[draftingZH7FK]

I realize this is born from not being completely up-to-speed on certain block Actions, but I was wondering if there is a way to reset/edit the Parameter point of an Action instead of deleting it and redrawing. I've been messing around with certain Parameters and Actions learning how the different base points work and it would be nice to just edit the base point like you can with the selection set and other properties. But, I haven't seen that in the menu or properties box. 

[Libbya]

As far as I know, the only ways to change which point an action is associated with is to either delete the action and remake it or delete the parameter, remake it, and re-associate the orphaned action with the new parameter.  

[h_s_walker]

Is the below what you're looking for?

[draftingZH7FK]

Not exactly. It's the red X shown in these snips which I can't find a way to edit or move after they're placed. From what I was learning about the XY stretch yesterday, if I place the point in certain corners, I think it affects how the object stretches and where it anchors so to speak. So if I accidentally pick the wrong corner, select my area and objects and then realize I messed up, I have to do it all over again as Libbya mentioned above. If I do this enough, it's a moot point but the trial and error as I made my different blocks was time-consuming. 

  

[Libbya]

I don't think that's what they are asking for.  I think they are asking if there is a way to change the parameter point that an action is associated with other than replacing either the action or parameter.  Imagine a stretch action that is associated with one of the (4) points of an XY parameter or one of the (2) points of a linear or polar parameter, but then you realize you associated it with the wrong point.  How can you change which point it is associated with? 

[Libbya]

FWIW, this is often more of an issue when someone starts using lookups or block properties tables to control parameters.  In that situation, the base point of a parameter is not altered, but the end points are.  If one has oriented the parameter and actions the 'wrong' way and associated actions with the base point of the parameter, then the lookups/BPTs will not function.

[xiandavis]

I'm tearing my hair out over this. A couple of days ago I successfully created DYNAMIC BLOCK 1. In DYNAMIC BLOCK 2, no matter what point I pick from left to right, the right most point is always selected. I was successful a couple of days ago, but I cannot get the left most point on THREAD ARRAY to be acted on (red X).

I looked on Autodesk about creating actions/ chain action, but I didn't find it satisfactory; is there an order parameters and actions should be created when multiple parameters are involved (i.e. create a parent linear parameter with stretch action  THEN create a child linear parameter with array action and THEN change the child's chain action to YES)? I'm not understanding dynamic blocks well enough to reliably replicate results.

Just created TEST, and I can get that to work correctly despite the red X being on the right point. I need help getting DYNAMIC BLOCK 2 to work like DYNAMIC BLOCK 1 and TEST.

[Libbya]

For the array to function you need to include the parameter (that is associated with the array) in the selection set of the stretch action.  Doing that shows another issue, you are both arraying and stretching the thread that is close to the point which causes the entire array to be moved and creates the new arrayed threads beyond the point.  There are various ways to solve that issue.  Probably simplest is to copy that thread on top of itself, stretch one copy of the thread, and array the other.

[xiandavis]

Oh wow. Ok, getting tricky. Thank you for the thoughtful reply.

Having trouble wrapping my head around including the linear param w/ array in the stretch action set, without stretching the array (see updated block).

[Libbya]

You need your stretch window to surround 1 and only 1 of the two points of the chained parameter. 

Here's an explanation of the current behavior.  The stretch window determines which vertices of an object are stretched and which are not stretched.  Vertices within the window are stretched and vertices outside the window are not stretched.  If a stretch window either entirely surrounds an object or does not surround any part of an object, the object is moved rather than stretched.  With your current version of the block, you are surrounding none of the points of the chained parameter, which results in the parameter just being moved.  Because it is moved, the length of the parameter is not changed and so no additional arrayed items are created.

[xiandavis]

'You need your stretch window to surround 1 and only 1 of the two points of the chained parameter.' was key.

I dragged both the thread param with array action and the thread linework over the stretched thread, then shifted the param with array action so one point was inside the already established stretch window.

Thank you so much for the fast and thorough guidance, Libbya. Great stuff.