Oddities entering position values

[chris.eganY2EK3]

This is a change from a week or two ago. When my grid is set to inches, the input boxes for position of an element are now very picky about how they'll accept entries. I can't start any entry with something that isn't a number. So I can't type ".5" I have to type "0.5". That alone isn't terrible, but it means you can't type in negative values directly, you have to enter a number, then arrow back and add the negative. It also won't let me fully delete a value before entering a new one, it refuses to delete the first number until I input another and then again arrow over and delete the first one. 

With units set to mils I see the same issue with it not accepting a negative symbol or decimal before a number is entered, but obviously you don't use a decimal as often in that unit system. 

This was not a problem previously, so I'm not sure what changed. I do not see this same issue in the other fusion workspaces, only electronics. 

[robert.martinUKYP4]

I'm glad it's not just me going mad over this.

The negatives are especially annoying to me as it worked perfectly before

[jorge_garcia]

Hi @robert.martinUKYP4 ,

I hope you're doing well. I can duplicate this, it's a very odd situation.

@HelenChen-ElectronicsQA I think this needs a ticket. The fact that a field doesn't let you enter a negative sign is really strange.

@robert.martinUKYP4 @chris.eganY2EK3 Thanks for letting us know about this.

Best Regards,

[HelenChen-ElectronicsQA]

Hi @chris.eganY2EK3 , @robert.martinUKYP4 , @jorge_garcia ,

Thank you very much for your reporting and sorry for any inconvenience.

I just logged a ticket about this.

As a workaround for the negative value input, please input the positive value firstly, and then click the cursor in front of the positive value in the Positive edit box, then input - to make it as negative value instead.

Hope it helps a little.

Regards,

Helen

[ritste20]

I had noticed this a couple of weeks ago as well. Very annoying to not allow negatives in value input.

https://forums.autodesk.com/t5/fusion-360-electronics/smd-pad-placement-can-t-start-with-a-negative-... 

Regards,

[robert.martinUKYP4]

I have found another weirdness with the co-ordinate system. A lot of work we do is laying out LED arrays to be uniform so positional spacing has to be very important. A strange problem I have found is that if I have accidentally placed a component in the correct position in Y, when selecting a row of components to enter the Y co-ordinate to correct the height of the remaining LEDs on the row, none of the components move. This is a minor inconvenience as I just have to change a number to move them all but it is still strange.

[ritste20]

That is strange. I can't say I've run into that but it sounds like by selecting the row it is treating them as a group. Since one component is at the correct dimension it decides that no change is needed. By moving them to an arbitrary dimension and then back it recognizes a change is required.

@jorge_garcia Can you shed some light on this? I would think that when the selected components have different coordinate values and the box shows as blank in the properties window, whatever is entered in the box would overwrite the parameter value and not just be ignored.

Regards,

[chris.eganY2EK3]

I have seen this too recently, but I always assumed that it was just that one of the parts being moved had something blocking it like a clearance violation, so it didn't move. But that doesn't always seem to be true. No idea if it's related or not. 

[robert.martinUKYP4]

I believe that must be exactly what is happening. It seems too consistent to just be a glitch.

@jorge_garcia I think Ritste20's suggestion as a fix would be a good implementation

[jorge_garcia]

Hi everyone,

What Steve mentions is what should happen by design. @robert.martinUKYP4 when you form the group, does the y coordinate in the inspector go blank? If it does then you should enter the value in that field and they should all move.

Does the field not go blank? If it doesn't try using the selection filter and make sure you can only select Parts and try again.

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

Best Regards,

[robert.martinUKYP4]

The selection field goes blank but if I enter a value that one of the selected components is already at, none of them move. If I enter a different value, they will move. I suspect this is not intended behavior

[jorge_garcia]

Hi @robert.martinUKYP4 ,

I think that might be an issue, I'm going to see if I can duplicate it and then report it.

Best Regards,

[chris.eganY2EK3]

The issue of not being able to enter any values starting with a negative sign still exists, along with not allowing you to fully delete an existing value before entering a new value. The field forces you to leave some integer, which often means you have to enter a value, delete the value it kept, then keep entering your new value. 

[HelenChen-ElectronicsQA]

Hi @chris.eganY2EK3 ,

Sorry for any inconvenience.

This issue is not addressed yet... We will keep you be posted if we have any update about this.

Regards,

Helen

[kevin2MSFQ]

@HelenChen-ElectronicsQA : I make footprints frequently and need to enter both positive and negative numbers in the process.  Each time I trip over this, it makes me frustrated.

This bug has remained unresolved for many months.  The fusion team needs to really internalize that each bump like this in the workflow is not only annoying, but injects costly errors into the workflow.

I see a ticket has been issued about this, when can we expect this bug to be fixed?

[HelenChen-ElectronicsQA]

Hi @kevin2MSFQ,

So sorry for any inconvenience.

I am sorry that the issue is not fixed yet.

Workaround is to enter a number, then arrow back and add the negative directly.

We will keep you be posted once this issue is fixed.

Thank you very much for your understanding.

Regards,

Helen

[HelenChen-ElectronicsQA]

Hi @robert.martinUKYP4 ，

Hope all is well.

For the issue you reported ago, in yesterday's Fusion new version 2.0.15291 we have put a fix into it.

Could you please upgrade to latest version and have a try? 

Hope it helps and hope you have a great day.

Best regards,

Helen

---

@robert.martinUKYP4 wrote:

I have found another weirdness with the co-ordinate system. A lot of work we do is laying out LED arrays to be uniform so positional spacing has to be very important. A strange problem I have found is that if I have accidentally placed a component in the correct position in Y, when selecting a row of components to enter the Y co-ordinate to correct the height of the remaining LEDs on the row, none of the components move. This is a minor inconvenience as I just have to change a number to move them all but it is still strange.

---