This object is in archive!
Sync widget with app (for recording)
Solved
I'm not sure if it's a problem with Locus Pro or a wrong procedure by me (probably the latter) .
I started recording a track inside Locus (main app) and then minimized. Correctly the application remains in background and continues storing data (there is the icon in the status bar).
What I'm asking is whether it is normal that the widget is "unlinked" with the app: it does not show the current distance count, the time, etc. and the recording and pausing buttons state is inconsistent (it looks like it's stopped, but actually the app is running and storing data so I should have the pause button and stop button available).
Thank you very much!
The same problem 
Good day,
such issue cannot be on your side, so no worry. Are you using latest 3.11.x version of Locus? This problem bother me for a very long time and I still cannot solve it correctly interesting.
Thank you for your report, I'll try to invest some more time to test it again.
Good day,
such issue cannot be on your side, so no worry. Are you using latest 3.11.x version of Locus? This problem bother me for a very long time and I still cannot solve it correctly interesting.
Thank you for your report, I'll try to invest some more time to test it again.
Thank you for the fast answer.
Yes, the latest 3.11.2 (Pro) . Is there some logging that I can send you? On the support options of the app there are only web links.
Thank you for the fast answer.
Yes, the latest 3.11.2 (Pro) . Is there some logging that I can send you? On the support options of the app there are only web links.
Thanks for offer, but in this case, log won't be useful. I have to test it by myself and search for break point that cause, that widget stop react on application events. Here log cannot help.
----
Later ... I was searching for cause of this problem and for unknown reason I have found changed one serious parameter in code, that should just connect new instance of Locus (after fresh start) to already existing widget. Hmm weird. So thanks for your report, should be fixed in next version!
Anyway because as I wrote, I have a long therm problems with widgets, feel free to write me if any problem with it remains! Thanks
Thanks for offer, but in this case, log won't be useful. I have to test it by myself and search for break point that cause, that widget stop react on application events. Here log cannot help.
----
Later ... I was searching for cause of this problem and for unknown reason I have found changed one serious parameter in code, that should just connect new instance of Locus (after fresh start) to already existing widget. Hmm weird. So thanks for your report, should be fixed in next version!
Anyway because as I wrote, I have a long therm problems with widgets, feel free to write me if any problem with it remains! Thanks
I suspected that the log wasn't enough to troubleshoot, but I thought that maybe you put some "tracing" around to be able at least to reproduce the problem, that's why I asked. :-)
It is also the first time I have seen this issue, because normally I start recording from the widget and then I move to the main interface. This time instead I did the reverse.
Thanks for your help and please make a note on the release log of the version that should fix the issue so that I can tell you if it's working or not. Bye
I suspected that the log wasn't enough to troubleshoot, but I thought that maybe you put some "tracing" around to be able at least to reproduce the problem, that's why I asked. :-)
It is also the first time I have seen this issue, because normally I start recording from the widget and then I move to the main interface. This time instead I did the reverse.
Thanks for your help and please make a note on the release log of the version that should fix the issue so that I can tell you if it's working or not. Bye
Replies have been locked on this page!