Moving selection with arrow keys not working

[infinitemach]

In the November 2022 update, moving selected assets with the arrow keys was a new feature. I have tried to use it, but I am unable to move a selected component, or any other selected asset with the arrow keys. I am running the latest version of F360 on Windows 11 Pro and a standard PC keyboard.

[panpan_fan · Accepted solution]

Hi @infinitemach 

I hope you are doing well!
I have quick try and the moving with arrow key works well for me.

I guess you may not activate the Move command when you use the arrow key.

Would you mind activating moving command and then selecting the component to move?

If the arrow key still can't work, it would be great that you can attach a short video to show. Thanks!

Regards,

Panpan Fan

[infinitemach]

Okay, yes, if I invoke the Move command first, I can move items with the arrow keys. My expectation is that once I select something, I should be able to move it with the arrow keys, just like the way it works with the mouse.

[phillipD6FQH]

This STILL isn't working for me. I created a new file. I placed a 2-point rectangle on it. I selected the whole box by dragging around it. I pressed 'm' to enter move mode - the usual move symbols showed up. I tried the arrow keys and they had no effect at all. I then used mouse to move (move mode still active) and it worked fine.
Is this something that used to work and doesn't now, or is there something I'm missing?

[jorge_garcia]

Hi @phillipD6FQH,

I hope you're doing well. When the MOVE command is active, left click the center of the component. At this point you can use the arrow keys to nudge it around, however if you use the mouse and move the component you will now be in "mouse" mode and the arrow keys will not be available. You can't switch between mouse and keys, whatever first moves the component, controls movement until you drop the component.

Sorry for being so verbose, if you try the above does it work for you? I just tried it and it works.

Let me know if there's anything else I can do for you.

Best Regards,

[infinitemach]

I don't understand why there needs to be a "mode" when moving. If something is selected for moving, I would expect both mouse or keyboard to work.

[jorge_garcia]

Hi @infinitemach,

So mode is just what I referred to them as. Both mouse and keyboard work the problem is that you can't switch between them. So for example, if you moving a part with the mouse and you get it into the general area you want at this point you can't use the arrow keys to fine tune. You would place the part and then select it again and use the arrow keys. The fact that you can't seamlessly switch between the two is probably where the confusion lies.

Let me know if there's anything else I can do for you.

Best Regards,

[phillipD6FQH]

I just tried it again, and no, I can't get anything to move with the arrow keys. I've been using computers since (probably before you were born) a MITS Altair in the mid-1970s (love those switches & lights), so I'm pretty comfortable with this stuff. I'm really stumped on this.

Some programs (Adobe InDesign comes to mind) even have settings for how far to move with each keypress AND how far to move with the SHIFT key pressed along with an arrow. Also, they don't have any limitations on mouse vs keyboard, you can use either on the same object without selecting. Same with all the electronics CAD software I have used over the years.

[jorge_garcia]

Hi @phillipD6FQH,

Yep, definitely before I was born😀.

So at this point, I'm going to ask you for more details about your computer setup. What OS are you running? What's the make and model of the machine? Is there anything unique about your keyboard or mouse setup?

Any info you can provide will help us get to the bottom of this.

Best Regards,

Jorge Garcia

[duncanBC5DV]

I have also used pretty much every EDA package around, and having similar issues. Windows 10 / Ryzen 1700 / 16GB / Samsung 970 SSD / FirePro graphics, Microsoft keyboard & Logitech mouse. Drivers and F360 all up to date.

I would really like to know the thought process that lead to thinking it was preferable to click on an object, select move tool, and then move it. Click and then use arrow key is standard.

Also, selecting a group and then using arrow keys should work but doesn't, but selecting a group and then click-dragging with the mouse does, without selecting move tool. These kind of inconsistencies are super frustrating, it's forcing the user into a predefined method instead of allowing flexibility. Rant ended.

[jorge_garcia]

Hi @duncanBC5DV,

I have created a ticket for this issue to be addressed. With that said just want to make a small clarification. You don't have to click the object first. You can click Move > Select the object > Place it without having to re-enable the Move command. This is known as verb-noun and has been around for a long time. Many users are accustomed to Right-click on an object and select move, we support that workflow as well known as noun-verb. Over time users complained that they wanted to click and drag like they do in drawing programs so we supported that workflow as well. We are now supporting the use of arrow keys as well with the MOVE command itself. 

I recognize there is still room for improvement, but as the above shows, we are trying to be as flexible as possible.

Let me know if there's anything else I can do for you.

Best Regards,

[mad.macs]

I haven't found a way to nudge multiple components yet. Selection here works backwards from what I would expect. It would seem logical to select the components you want to move first, then use the keys, or grab one of the crosshairs of the component and move with a mouse. So many times I want to move 5 things a little to the left, and when you try to move them together with the mouse, it moves all over the place as soon as you select them.

[jorge_garcia]

Hi @mad.macs,

I hope you're doing well. Here's the procedure for this:

1) Form a selection

2) Activate the MOVE command

3) Ctrl+Right click a member of the group

4) VERY IMPORTANT DO NOT MOVE THE MOUSE press your arrow keys to bump the components in grid unit increments.

The key here is to not move the mouse, the move command accepts which ever input comes first keys or mouse and then sticks to it.

Let me know if you continue to run into problems.

Best Regards,

[robert_pellegrino]

This is the sort of thing that makes Fusion 360 a nightmare.  Decisions like this are a sign of engineering run amuck with no input from Product Management or UI groups.  When someone selects an object and it highlights, the expectation is that further operations will be applied to the object in a non-modal way. 

So, 1. click, 2. arrow nudge

Fusion 360 Electronics theoretically has everything it needs to be a world class replacement for Eagle.  All it needs is a product manager that lays out the marching orders to listen to the UX experts (if they employ any) and integrate consistently with the rest of Fusion.  Right now it is wearing a Fusion t-shirt, but isn't really part of the team.