Actually this is a bad idea!Let me start by saying I have no association with the development of LMT or @noname81, I am just a random person out on the internet. But he may chime in to say what a bad idea the following actually is :silly:
I had a thought of being able to paginate through different configs of LMT, from LMT. Maybe a "next page" or a tabulated type arrangement, so I tested the concept. I don't have a current need, but thought someone else might want to take this idea further.
I created a path (assume all scripts are run under su)
Created an LMT config using the interface, and copied the LMT.xml to the directory named as LMT1.xml
cleared out that config, and created a totally different LMT config and copied that to the new path
Now from a shell, I could switch between the different LMT configs using the scripts
And it seemed to work! :highfive:
Things that will make it more useful or improve it:
Create LMT interface items to automate the running of the scripts to switch between different LMT configs
Instead of a "kill" maybe a stop service would work and be more "polite"
At the end of the script, possibly a sleep and send a screen touch event to the hot-spot area to show/activate/display the new LMT
Conceptually in my testing it worked, and I also do not see any reason as to the practical limit of how many LMT's you could page through
PS: I am using LMT_v3.0_beta1.apk on Pie
Just a joke. If it's working for you it's fine. Just be aware that lmt reads the xmls just at app startup. So just restarting the service won't be sufficient. You have to (gracefully ) close and restart lmt.