Block with additional grips - the insertion point won't move with it

[Anonymous]

Here’s how I created the block:

1 – Drew it with the required layers

2 – Define the drawing as a block

3 – Part of that definition is the insertion point

4 – Save the block

Next I edited the block to add additional grips for moving the block as needed:

5 – Open the Block Editor

6 – Add points as needed

7 – Add the Move action

8 – Save the edited block

Now, when I move the block via any new grip, the block’s insertion point remains at the original location. With any subsequent moves, the insertion point still remains at the original location, which make it impossible to move the block via its “proper” insertion point.

What have I done wrong? Attached is a drawing containing the block.

[edburkett]

The solution is pretty simple. I just stumbled on it myself recently.

Add a Basepoint parameter at the insertion point.

Update the selection set for all of your move actions to include the newly added Basepoint.

Now, when you select one of your new grip points to move the block, the insertion point goes with it.

[Edwin.Saez]

@Anonymous,

Here you have. clue a "basepoint" parameter, then add to each selection set of the "move" action.

[Libbya]

I would add that there is a bug in the dynamic block code that causes issues with chained parameters if the basepoint parameter is moved directly.  The solution for that bug is to add a gripless chained point/move and add only the basepoint to the move's selection set.  You then add the chained point to the selection set of any actions you would like to work on the basepoint and *remove* the basepoint from those actions.  

[Anonymous]

The block provided by edwin.saez.jamanca works but I don't know how he did it.

Libbya, thank you for you explanation of how to bypass the "bug" but I can't seem to make it work (perhaps it's too early in the morning) despite several attempts. Would you be willing to provide a screencast? Thanks.

[Libbya]

This is how I would recommend addressing the basepoint in your block:  

[Anonymous]

Thank you very much for the screencast. It was very helpful.

You’re using Architecture 2017 and I’m using LT 2018, so the icons for “move” looks different but they probably work the same.

I’ve been able to follow along (with much pausing and rewinding) and here’s what happens step-by-step:

>It's pretty clear up to this point<

Command: _Bactiontool

Enter action type [Array/Lookup/Flip/Move/Rotate (etc.)]: _move

            BACTIONTOOL Select parameter:

(You clicked on the “Position2” leader)

The command line shows:

Select parameter:

Specify selection set for action

            BACTIONTOOL Select objects:

(You clicked on the leader a second time)

The command line shows:

Specify selection set for action

Select objects: 1 found

            BACTIONTOOL Select objects:

(You clicked on the Basepoint)

The command line shows:

Select objects: 1 found, 2 total

            BACTIONTOOL Select objects:

The command line shows:

BACTIONTOOL Specify action location or [Multiplier/Offset]

>That doesn’t show on my command line and it’s the point where I get lost<

On your drawing “Move1” with a lightning bolt appears.

Mine instead shows a gray box with a tiny lightning bolt in the middle of direction arrows. It

 appears where AC “wants” it.

(You clicked on the spot where you want the lightning bolt to be)

The leader for “Position2” changes direction

The command line shows:

Select objects:

Specify action location or [Multiplier/Offset]

(You clicked on the leader)

The command line shows:

** STRETCH **

Specify stretch point of [Base point Copy Undo eXit]:

(You clicked on the basepoint)

The leader changed direction, you clicked on the end of it and dragged it to the basepoint.

The command line shows:

*Cancel*

The rest seems pretty clear but where/how have I failed?

Thanks!

[Libbya]

At 0:35 I don't actually click on the Position2 leader, I missed...  That's the reason I click on it right afterward 0:37.  

The differences you describe about the appearance of the actions and the menu options in the command line are because you have the system variable BACTIONBARMODE=1.  I have it =0.  That doesn't have any effect on the function of the block.  It also doesn't change the solution to how I made the block work. 

At 0:42, the Position2 parameter does not change on its own.  I select the parameter and move its base location to the 0,0 point on top of the Basepoint parameter.

I really can't say how you failed because you didn't post the block or a screencast showing the steps you took.  Any comment of mine would just be a totally wild guess.

[Anonymous]

I haven't posted the block because I didn't save the changes I tried to make, but I'm willing to do it again and save at that point. I'll change the setting for BACTIONBARMODE to 0 and try to do a screencast but I've used up all of today's "research time" that my boss allows (darn him).

Thanks again for your help.

[Libbya · Accepted solution]

The basepoint parameter is added to the block at 0,0.  Whenever you add any actions, you make sure that the base point is not included directly in the selection set of any actions in the block, ever.  If you want the basepoint's location to be affected by an action, then you add a position parameter right on top of the base point location.  You change that position in properties so that it is 'chained' and so that no grips are visible.  You add a move action to that position parameter and include the base point in its selection set.  You then add that chained gripless point/move to the selection set of the action(s) you wanted to affect the basepoint position.  What part of the process or function do you find confusing?    

[Anonymous]

I used to be very skilled with AC but for the last 2-1/2 years I've been stuck using Visio to create very simple (and ugly) single-line diagrams. My boss finally wants to transition to cad but I only have an hour or two to work toward a new system, and the rest of the day is spent with my usual tasks. He gets to decide how my time is used. Adding grips is something I've never done and I'm obviously struggling, which is why I appreciate your help. Once I get it mastered I can show the results to my boss and hopefully be allowed to spend more time creating a library and a tool palette and some decent drawing standards.

Tomorrow is a new day but for now I have to create ugly things to keep the boss happy.

[Anonymous]

OK, I'm an idiot. Despite your helpful screencast and patience, I'm missing something. For the moment I'm going to step away and work on other things. I appreciate what you've done and thank you very much for taking the time.

[zbysogi]

I have a block with visibility states:

Whenever I move the block and change the vis state the visibility dropdown menu point moves and the block doesnt change accordingly to the position of the basepoint  and to the way it is built within the block (it seems to expand both left and right instead just to the right):

Basepoint, visibility parameter as well as the green point, all moved 😕

[edburkett]

The problem with your block is that you didn't include the elements in the non-visible states in the move actions. So, when you move the block via one of the point grips, you're only moving the elements in the current visibility state. The elements in the non-visible states, including the point parameters in those states, stay where they are. The basepoint and visibility grips always move because they are visible in all states and included in all of the move actions.

The solution is to set Visibility Mode (BVMODE) to 1 (on) then modify the selection set for all of the move actions to include all elements in all visibility modes.

I've never done anything with chained parameters/actions so I don't fully understand Libbya's post. But it doesn't appear you are using chained in this block so it shouldn't matter. When not using chained, there's no need for the additional point parameters or move action at the insertion point (0,0). As long as the basepoint is included in all of the move actions it will move the insertion point with it. Also, since it's always in the same relative position to the insert point, there's no need for the additional point parameters at the upper-left location. A single point parameter at that location that is visible in all states will get the job done.

I'm pretty sure the attached works the way you intend.

[Colin-Pearson]

OLD POST, BUT THANKS FOR THE TIP ON THE CHAINED PARAMETER TO MOVE THE BASEPOINT!