Coord[].TimerEnabled

[wehg]

I have two different applications/projects where the Coord[].TimerEnabled move timer status is behaving differently. In the first application if I feedhold a move using quick stop (lh\) or 'hold' command, the move stops as expected and the move timer status goes to 0, which allows the in-position status to go true, and all is well. In the second application, if I feedhold a move using the same commands, the move stops as expected, but the move timer status remains 1, which prevents the in-position status from going true. Any thoughts on what might cause this difference in behavior? My real issue falls in the resulting difference in 'in-position' behavior. In both cases the move execution resumes fine with a 'run' command. As a side note, if in the second application the move is stopped with a 'pause' command allowing the current move to finish, the move timer status goes to 0 as expected.