Move object along the line malfunction

[Julio]

Hi everyone,

 

A nasty "snap to nearest" problem here that may have a quick solution through some variable.

 

I'm trying to draw a 20m long line along an existing diagonal xline. 

- I chose a point of departure on the xline, OK

- For the second point I hover above the xline until "snap to the nearest" appears,

- I type the value "20", and normally would hit "Enter" to complete the command,.... but as soon as I type "20", the snap mark disappears, and hitting "Enter" leads to a wrong, imprecise point. However, I do get a precise result if I first type "20" and only then hover on the Xline until the snap mark appears and I hit "Enter".

 

This little inversion of order in the existing DWG file was sudden and affects all types of snap and all objects. It also affects MOVE or COPY and other commands, for ex. move object along the line. It plagued also the new files, thus I guess it's a system variable problem.

 

Ortho mode is off. The versions are 2017, 2018 and 2019.

 

Please help!  I'm an intense AutoCAD user for 20 years but don't remember having this. A tiny problem of this kind totally ruins my automatism and drafting routine.

Thanks in advance!

Julio 

[eldon]

Have you tried investigating the PICKFIRST system variable?

[Julio]

Just tried now PICKFIRST with 0 and 1 values, without any effect on the problem...

The problematic inversion of the order is between two steps after the command is already launched. PICKFIRST on the other hand deals with choices before launching a command.

But thanks all the same, Eldon!

Julio

[Julio]

So far the variable OSNAPCOORD seems to bring the magic solution for the folks who described their problems in very similar terms. But nay, I tried all 3 values, with rebooting Acad in between, nothing  seems to help it...

Any other ideas, Acad savvys?

Julio

[Julio]

Ok, someone just offered me a magic and inexplicable solution in another forum:

All you have to do is to dock your floating command line.

Seems totally unrelated, but worked like charms. Apparently, it's a known bug since 2013 v

 

[ammobake]

Wierd.  There are similar issues in civil 3d relating to the properties bar and they've never been fixed either.

-Chris

[BIGAL]

If you look into snapang it will let you do what you want. nearest nearest then f8