John Thompson
Well-Known Member
If Localization is available as a hard button I see no need for it on the Home screen. I'm with Jim.
I agree with this reasoning. I was trying to think of which home screen button could be sacrificed to make room for Localization (which is not necessary if it has a hardware button). I never use the Data Exchange button - I always get to it from Files or Points. But Data Exchange is a basic function that merits a spot on the Home screen. I suppose if room needs to be made on the Home Screen (and I'm not sure it does), there are other buttons that could be moved inside the System button or a third Home Screen could be added.The issue is which functions rate top-level access. I'm lobbying in favor of leaving Data Exchange as a one-push function due to its frequency of use.
If Localization is available as a hard button I see no need for it on the Home screen. I'm with Jim.
Us too! Daily. Multiple times a day in fact. We use it out in the field on the job multiple times.I vote for Data Exchange on home screen. We use it every single day. We transfer all data to/from the LS through google drive so Data Exchange is a top tier button.
As a side idea suggestion regarding codes:
What if the traditional grid view was used but the top row of buttons toggled between customizable categories. Essentially like customizable pages of codes.
I do create the localization there when I'm importing a deed description or prior survey, usually in the form of linework in a dxf file. I'm referring to the need to access the localization multiple times in the field to add each point as it is collected and link it to a corner of the linework on that page.You can create a localization from the screens where you change the project or page coordinate systems so why not just do it there?
Unless I misunderstand what you are suggesting, that is exactly how I use the Category to show button. My codes are categorized and it's one more click than what you describe, but it works well for me.What if the traditional grid view was used but the top row of buttons toggled between customizable categories. Essentially like customizable pages of codes.
We hide the parameter in the user mode. By default the parameter has "0" value (unlimited distance). It could be that in your profile it has a different value. You can set an engine parameters to the default values by pushing the "To Default" button on the bottom row of the screen.I am about 29 km from a station, I get the message "far from stdl" with the previous firmware you had to increase the FROM STDL value to 50 or more, with the latest firmware this option I can no longer find it. Has it been removed or is it still there?
Could you explain your workflow in more details - collecting points, collecting with offsets, CoGo or something else?Is there a way to set the store points in d to d offset to automatically move up to the next point? it did it before the 4.0 update.
He's describing the bug where the point number doesn't advance in the offset screen.Could you explain your workflow in more details - collecting points, collecting with offsets, CoGo or something else?
I have noticed that too.He's describing the bug where the point number doesn't advance in the offset screen.
yes this is itView attachment 12827
I found a bug: after collecting a point in Offset mode, the name of the resulting point does not increase. Do you mean this case?
Charles,