Darren Clemons
Well-Known Member
While many, many improvements have been made in the "auto" point numbering in the LS there are still several spots we're seeing some issues.
When starting a new job and importing, say, 40 design points it seems as though the collect screen could/should automatically come up with point 41. It usually has the next number I believe from the previous days work - for instance if the last point I shot in yesterdays job was 122 it will be on 123. This also applies to starting the base on the session point. I have to click the number, whatever it's on, then I'll typically just type in point 1, since I know it's been used and it will then auto increment to point 41. This, I have found, is the best way to get your "next number" in most all the collect screens, however, COGO screens seem to not always use this feature.
When using the offset, direct function within the collect screen, the point I store where I'm standing will be correct at the next point number - i.e. 50. Then when I click on the offset point at the bottom (defaults to C1) I'll input 51 (I don't like alphanumeric point numbers). Then, if I collect another offset, direct shot it correctly stores point where I'm standing at point 52 but when I go back in to store the next offset point it is also on point 52. First off it does not pick up that I've already stored 52, but it will actually store a "second" point 52 without a warning. Some screens will not allow a "duplicate" number to be stored while many others (most COGO functions) will allow it without any warning.
These are very minor issues but it is a pain most times always changing/checking and having to re number duplicate points. It just seems overall that the LS has difficulty always keeping up with what numbers have been used between different functions.
Anyone else having any other instances or is there any more fixes planned?
When starting a new job and importing, say, 40 design points it seems as though the collect screen could/should automatically come up with point 41. It usually has the next number I believe from the previous days work - for instance if the last point I shot in yesterdays job was 122 it will be on 123. This also applies to starting the base on the session point. I have to click the number, whatever it's on, then I'll typically just type in point 1, since I know it's been used and it will then auto increment to point 41. This, I have found, is the best way to get your "next number" in most all the collect screens, however, COGO screens seem to not always use this feature.
When using the offset, direct function within the collect screen, the point I store where I'm standing will be correct at the next point number - i.e. 50. Then when I click on the offset point at the bottom (defaults to C1) I'll input 51 (I don't like alphanumeric point numbers). Then, if I collect another offset, direct shot it correctly stores point where I'm standing at point 52 but when I go back in to store the next offset point it is also on point 52. First off it does not pick up that I've already stored 52, but it will actually store a "second" point 52 without a warning. Some screens will not allow a "duplicate" number to be stored while many others (most COGO functions) will allow it without any warning.
These are very minor issues but it is a pain most times always changing/checking and having to re number duplicate points. It just seems overall that the LS has difficulty always keeping up with what numbers have been used between different functions.
Anyone else having any other instances or is there any more fixes planned?
