"The nudge distance you entered is invalid"

**BobInce** · 19 September 2008, 05:21 PM

I add a new unit 'px' corresponding to 1pix, to avoid this problem.

**steve.ledger** · 19 September 2008, 07:55 PM

I've seen this happen in previous versions as well. It's a bug, sometimes the nudge units reset to zero when changing the unit type.
I've also seen the effect that each tab lists exactly the same options after this bug occurrs. Xtreme has to be closed and re opened for it to regain proper function.
I think Brian's 'px' (here) was a typo, he was only noting what the option read after he'd changed units.

**handrawn** · 19 September 2008, 08:03 PM

I switch pix/inch/mm a lot - never seen a bug like this - doesn't mean there isn't one of course

accidentally typing in px, or deleting the p when entering a value directly into the info bar - which gives the same/similar message - that I do a lot

**raynerj1** · 20 September 2008, 03:06 AM

If my default nudge is less than .1 then I will get this when I change units. I usually just close the dialog with the "x", then reopen and reset the nudge value. On one of the versions we could have a default value of .00001 and there would be no problem, the next rev out, tho... the error message was back.

**handrawn** · 20 September 2008, 08:28 AM

right - I don't work in units where less than 1 would be required for nudge - thanks for the info John

**dpt** · 20 September 2008, 03:28 PM

I've seen this happen when the the system-wide "No. of digits after decimal" setting has been reset to zero. (This happens on my system sporadically, and I've come to the conclusion that Opera's to blame.)

I fix it by going to Control Panel > Regional and Language Options > Regional Options > Customize... > No. of digits after decimal and setting it back to '2'.

**brianlj** · 20 September 2008, 11:14 PM

Originally Posted by dpt

I fix it by going to Control Panel > Regional and Language Options > Regional Options > Customize... > No. of digits after decimal and setting it back to '2'.

Absolutely correct!

Yes, the 'px' was a typo, but I've discovered that changing from another unit to pixels will produce the error message if the 'No. of digits after decimal' is set to 0.

So, I'm curious... why do you think it's Opera? I just happen to use Opera as well.