Menion,
Sorry to leave a comment. The form acts strangely in my browser and I no opportunity to write the main text.
I have been using the combo Locus Map Pro/ Gsak for Locus for years now. I know that Gsak for Locus is no more maintained nor on the Play Store, but even with phone changes (and android version changes) I was able to use my GSAK databases on my phone. Unfortunately, this is broken. I suspect that the last release of Locus 3.46.2 changed something in the communication between the plugin and the main program. Regarding my phone or OS no evolution took place for months, so this is not the problem. What are the symptoms? When using GFL (Gsak For Locus) with the currently selected database: everything works as usual. But when I want to switch to another database via the file selection dialog of GFL, the next screen is a “Locus Map stopped”. I know that GFL is old but it was working well since 3.46.2, so I guess something changed that messed up things here. I’ll be glad to hear that this behaviour can be reversed. Many thanks for time taken on that matter.
Menion,
Sorry to leave a comment. The form acts strangely in my browser and I no opportunity to write the main text.
I have been using the combo Locus Map Pro/ Gsak for Locus for years now. I know that Gsak for Locus is no more maintained nor on the Play Store, but even with phone changes (and android version changes) I was able to use my GSAK databases on my phone. Unfortunately, this is broken. I suspect that the last release of Locus 3.46.2 changed something in the communication between the plugin and the main program. Regarding my phone or OS no evolution took place for months, so this is not the problem. What are the symptoms? When using GFL (Gsak For Locus) with the currently selected database: everything works as usual. But when I want to switch to another database via the file selection dialog of GFL, the next screen is a “Locus Map stopped”. I know that GFL is old but it was working well since 3.46.2, so I guess something changed that messed up things here. I’ll be glad to hear that this behaviour can be reversed. Many thanks for time taken on that matter.
The same problem 
Hello zoumba,
you are not the only victim of this unwanted bug - sorry for this.
The issue already detected and fixed. New version is planned most probably on the next week. Sorry for the complications!
Menion
Hello zoumba,
you are not the only victim of this unwanted bug - sorry for this.
The issue already detected and fixed. New version is planned most probably on the next week. Sorry for the complications!
Menion
You don't have to be sorry. I am quite clear that all that stuff is complex. Also this is an old plugin so the weight of history is heavy clearly.
As long as we go back to the old behaviour in less than 3 years :-) this is great for me.
Don't rush take time and take care.
I must say I seen no issue recently raised when I searched for GSAK.
Sorry for duplicate issue. No need to answer this comment. I'm already pleased with what's done on Locus.
You don't have to be sorry. I am quite clear that all that stuff is complex. Also this is an old plugin so the weight of history is heavy clearly.
As long as we go back to the old behaviour in less than 3 years :-) this is great for me.
Don't rush take time and take care.
I must say I seen no issue recently raised when I searched for GSAK.
Sorry for duplicate issue. No need to answer this comment. I'm already pleased with what's done on Locus.
Replies have been locked on this page!