This object is in archive!
Additional Public Intents
Completed
Would be great if there were some additional public intents available in Locus. With these a person can create some voice controls using Takser + AutoVoice for hands free Locus Interaction. Very handy for any power sports applications and in winter (gloves).
Add quick/auto named waypoint (no user other user interaction required)
Zoom in
Zoom out
Rotate map
Show view
Load map by name
Toggle Hold map center
Thank you.
I like this idea 
I like the idea of expanding the number of public intents because it allows me to control Locus Map using an external app (even an external device). For example, I can create verbal commands to "Create Waypoint" and "Pause Recording".
I would like the existing Waypoint intent to be enhanced (perhaps using an optional parameter) so that it can automatically create a new waypoint without user-interaction.
Currently, it presents a dialog-box allowing the user to edit the waypoint's name. The optional parameter would change the intent's behavior so it automatically create a waypoint using the default name (Point1, Point2, Point3, etc) without any user-interaction.
Similarly, intents to control zooming and panning should also accept parameters dictating the amount of zooming/panning. For example, integer values of 1-10 where 1=10% and 10=100%.
If this were available, I could say "Pan Right" and the map would pan to the right by the amount I had programmed (5=50% of the screens width). If I say "Zoom In", the map would magnify by whatever amount I had specified (1=10% for vector maps or 1 level for raster maps).
I like the idea of expanding the number of public intents because it allows me to control Locus Map using an external app (even an external device). For example, I can create verbal commands to "Create Waypoint" and "Pause Recording".
I would like the existing Waypoint intent to be enhanced (perhaps using an optional parameter) so that it can automatically create a new waypoint without user-interaction.
Currently, it presents a dialog-box allowing the user to edit the waypoint's name. The optional parameter would change the intent's behavior so it automatically create a waypoint using the default name (Point1, Point2, Point3, etc) without any user-interaction.
Similarly, intents to control zooming and panning should also accept parameters dictating the amount of zooming/panning. For example, integer values of 1-10 where 1=10% and 10=100%.
If this were available, I could say "Pan Right" and the map would pan to the right by the amount I had programmed (5=50% of the screens width). If I say "Zoom In", the map would magnify by whatever amount I had specified (1=10% for vector maps or 1 level for raster maps).
i would also like the intent to open the compass and weather screens
i would also like the intent to open the compass and weather screens
very good idea
Zoom in,
Zoom out,
Load map by name (Identifying card names by language is difficult. Each card precedes a number. 1_BadenWuerttemberg, 2_Germany .... then I can say invite card 2)
As with Alexa or Siri. I say hello Locus and Locus switches to voice control and waits for commands.
Or you can make your own command by voice with the locus then switch to voice control.
very good idea
Zoom in,
Zoom out,
Load map by name (Identifying card names by language is difficult. Each card precedes a number. 1_BadenWuerttemberg, 2_Germany .... then I can say invite card 2)
As with Alexa or Siri. I say hello Locus and Locus switches to voice control and waits for commands.
Or you can make your own command by voice with the locus then switch to voice control.
what might be better is to combine with the new profiles
set up a profile to load a certain map, then call profile with intent
i could see this being very usefull
if combined with tasker, you could then say "locus load bike " etc etc
what might be better is to combine with the new profiles
set up a profile to load a certain map, then call profile with intent
i could see this being very usefull
if combined with tasker, you could then say "locus load bike " etc etc
An intent to select maps would require a non-optional parameter for "map name". The "map name" must be spelled the way it appears in Locus's list of maps (and it must be in whatever language you use).
For example, in English, the AutoVoice macro could be something like "Show Map Cycling" and it would transmit a Map intent with the parameter "OpenCycleMap".
An intent to select maps would require a non-optional parameter for "map name". The "map name" must be spelled the way it appears in Locus's list of maps (and it must be in whatever language you use).
For example, in English, the AutoVoice macro could be something like "Show Map Cycling" and it would transmit a Map intent with the parameter "OpenCycleMap".
The future is voice control. Siri, Alexa, Bixby. The new Bixby from Samsung should surpass everything else. There is a separate button. Perhaps you can use this for such a function.
Let's wait a few weeks and look where the way goes.
The future is voice control. Siri, Alexa, Bixby. The new Bixby from Samsung should surpass everything else. There is a separate button. Perhaps you can use this for such a function.
Let's wait a few weeks and look where the way goes.
Unless Samsung's Bixby is available for all Android phones, and comes with an API, and can work without an Internet connection, it is not a good option for Locus Map.
Google plans to release an API for Google Assistant. Developers will be able to create custom Actions. However, I don't know if these Actions will require an Internet connection to process them.
https://developers.google.com/actions/
Unless Samsung's Bixby is available for all Android phones, and comes with an API, and can work without an Internet connection, it is not a good option for Locus Map.
Google plans to release an API for Google Assistant. Developers will be able to create custom Actions. However, I don't know if these Actions will require an Internet connection to process them.
https://developers.google.com/actions/
Good day guys,
quite old idea I would like to close based on few facts:
1. we have for some time very nice add-on from @falco ,
add-on is on Google Play or you may check author repository. Falco is very active here on forum, so I'm sure, he will appreciate some feedback!
2. New API system for Locus
For some time, I'm working on an improved system for communication with Locus. More about this is here . I'll be happy to improve this system if there will be interest. At bottom are some samples, so feel free to test and use it ;).
As I see, except "load map by name", all tasks from initial idea here may be implemented with this API.
Good day guys,
quite old idea I would like to close based on few facts:
1. we have for some time very nice add-on from @falco ,
add-on is on Google Play or you may check author repository. Falco is very active here on forum, so I'm sure, he will appreciate some feedback!
2. New API system for Locus
For some time, I'm working on an improved system for communication with Locus. More about this is here . I'll be happy to improve this system if there will be interest. At bottom are some samples, so feel free to test and use it ;).
As I see, except "load map by name", all tasks from initial idea here may be implemented with this API.
Replies have been locked on this page!