This object is in archive!
Adding "Instant EXIT" function
Completed
This function will exit Locus even when all these Live tracking and Track recording features are turned ON.
It is critical when you are in need of restarting Locus, for example you changed a config file and now you want it to reload or you need to test/debug something.
Nowadays, people are killing the Locus process by external applications. This is really not cool. Locus should have its own clean EXIT mechanism.
PS. After every Locus EXIT, if that happened during track record, recoding should start itself automatically after returning to the application. Locus should just remember what was happening and was features were turned on before EXITing, and then restore everything.
I like this idea 
Well... to be honest... I think exit & restart should never be neccessary in the first place. It`s simply a "workaround" because Locus doesnt automatically(!) recognize and re-read changed config files, map directories, map items, etcpp.
And since it is only a workaround (until menion implements the realtime file/drawer notifications), we might just as well keep using a hacky FORCEQUIT by whatever means available. Some ROMs/MODs for example FORCEQUIT an app if you longpress the BACK button. Very convenient.
Another question is Locus behaviour when restarted after a force-quit or phone-reboot. IMHO, as you suggest correctly, it should go back to exactly where it was before. Track recording (if active) should be restarted immediately, not in pause mode. Live tracking (if active) should be restarted. All map items etcpp should be restored (i guess that works already).
I would even go one step further on this: if the phone crashes and reboots for whatever reason when Locus was running, why not automatically restart the app and continue track recording (etc)?
After all, a properly recorded track can literally mean the difference between life and death. Or a bit less dramatic: an easy decent on dangerous glacier in a major whiteout vs a very inconvenient and horribly cold emergency bivy until the skies clear up again next morning.
Well... to be honest... I think exit & restart should never be neccessary in the first place. It`s simply a "workaround" because Locus doesnt automatically(!) recognize and re-read changed config files, map directories, map items, etcpp.
And since it is only a workaround (until menion implements the realtime file/drawer notifications), we might just as well keep using a hacky FORCEQUIT by whatever means available. Some ROMs/MODs for example FORCEQUIT an app if you longpress the BACK button. Very convenient.
Another question is Locus behaviour when restarted after a force-quit or phone-reboot. IMHO, as you suggest correctly, it should go back to exactly where it was before. Track recording (if active) should be restarted immediately, not in pause mode. Live tracking (if active) should be restarted. All map items etcpp should be restored (i guess that works already).
I would even go one step further on this: if the phone crashes and reboots for whatever reason when Locus was running, why not automatically restart the app and continue track recording (etc)?
After all, a properly recorded track can literally mean the difference between life and death. Or a bit less dramatic: an easy decent on dangerous glacier in a major whiteout vs a very inconvenient and horribly cold emergency bivy until the skies clear up again next morning.
My god, you are reading my mind. I totally agree with ALL what you said above. I was also thinking about automatic restart of the whole application:)
My god, you are reading my mind. I totally agree with ALL what you said above. I was also thinking about automatic restart of the whole application:)
My god, now you`re two on me ... it will be looong autumn/winter, but we will make from Locus usable app, I`m sure ;)
EDIT: to give here also some more "professional" opinion, not just bul***ts. Agree, restoring previous state is necessary. Not sure if everything even after restart (restart has usually some reason. If reason was Locus, then restart should lead to cycle ...), but most yes ...
I`ll think about some automatic checking of changes in filesystem. I`m personally not a big fan of it. It`s usable mainly for hardcore users. Basic users do not need change config file at runtime etc. Many features are initialized from config parameters at start, so it should also be a quite a lot of work (I know, my problem)
Anyway, generally agree ...
My god, now you`re two on me ... it will be looong autumn/winter, but we will make from Locus usable app, I`m sure ;)
EDIT: to give here also some more "professional" opinion, not just bul***ts. Agree, restoring previous state is necessary. Not sure if everything even after restart (restart has usually some reason. If reason was Locus, then restart should lead to cycle ...), but most yes ...
I`ll think about some automatic checking of changes in filesystem. I`m personally not a big fan of it. It`s usable mainly for hardcore users. Basic users do not need change config file at runtime etc. Many features are initialized from config parameters at start, so it should also be a quite a lot of work (I know, my problem)
Anyway, generally agree ...
Menion, most or all of my Locus wishes during last two years are implemented now. So Locus is usable app:) We are just trying to motivate you to make is perfect:) And you are on a right path to do accomplish that. Look at the iPhone map apps... Their users are jealous because of Locus. Pro version of Locus should be named "Locus Mighty" :)
Menion, most or all of my Locus wishes during last two years are implemented now. So Locus is usable app:) We are just trying to motivate you to make is perfect:) And you are on a right path to do accomplish that. Look at the iPhone map apps... Their users are jealous because of Locus. Pro version of Locus should be named "Locus Mighty" :)
Obviously, auto-restart after crash/reboot has its dangers. This might be a good place to throw one your beloved dialogs into our faces beforehand :-).
---
Locus was terminated while BLA was active What do you want to do?
[Restart Locus with BLA activated]
[Restart Locus with BLA paused]
[Abort]
10...9...8... countdown until highlighted choice will run automatically.
---
BLA is replaced by
"track recording" or
"live tracking" or
"track recording and live tracking".
The dialog would automatically remember the last choice.
Obviously, auto-restart after crash/reboot has its dangers. This might be a good place to throw one your beloved dialogs into our faces beforehand :-).
---
Locus was terminated while BLA was active What do you want to do?
[Restart Locus with BLA activated]
[Restart Locus with BLA paused]
[Abort]
10...9...8... countdown until highlighted choice will run automatically.
---
BLA is replaced by
"track recording" or
"live tracking" or
"track recording and live tracking".
The dialog would automatically remember the last choice.
Because main idea of this "Idea" was ability to close Locus even if some features are currently running, I'm closing it as "Implemented".
Second idea that comes up from discussion is to restore previous state, but mainly for me and also to give at least some votes, I suggest to create a separate idea for this, or check if anyone already posted it.
EDIT: by implemented, I mean new "Close dialog" in latest Locus version (2.19.1+)
Because main idea of this "Idea" was ability to close Locus even if some features are currently running, I'm closing it as "Implemented".
Second idea that comes up from discussion is to restore previous state, but mainly for me and also to give at least some votes, I suggest to create a separate idea for this, or check if anyone already posted it.
EDIT: by implemented, I mean new "Close dialog" in latest Locus version (2.19.1+)
Replies have been locked on this page!