-
-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stakeout precise view - Not showing anymore the position of the receiver #5021
Comments
@Catalin75 , could you attach a video capture of what you see on Borneo? |
At this moment I cannot. Yesterday I noticed that, when trying to stakeout a point, the blue dot didn't appear at all, and when I got very close to the point to identify, the trigonometrical circle turned green entirely, for a short moment. Also, the documentation referring to the stakeout on qfield.com says that this is how stakeout should happen (no reference to the dot representing the receiver). |
@Catalin75 , just tried with QField 3.1.9 on Android, and I can see the point: Something specific to a project of yours might be at play. You'll need to provide a sample project and a video to facilitate looking into this. Thanks. |
@Catalin75 , that was exactly the kind of details that was needed. Fix incoming here: #5023 |
@Catalin75 , if you have a minute, please confirm the regression has been fixed using this test APK: #5023 (comment) -- thanks. |
I am really sorry, but until Monday, 12.02.2024, when I will get back to work, I will not have acces to my tablet. |
@Catalin75 , no problem, you'll have something to look forward to going back to work ;) Out of curiosity, what are the way(s) your company is using QField? |
Good morning ! |
@Catalin75 , by end of February, the new version should be out. |
With latest update (Borneo), the stakeout precise view does not show anymore the position of the receiever, (the blue dot in the image attached). This makes more difficult the stakeout of a feature, which now should be realised through distance and bearing only, without any visual help.
The text was updated successfully, but these errors were encountered: