Messages

For all the functions offering access to the list of Android ringtones, such as, "Ringtone 1st fix", "Alarm near waypoint", etc....  the application systematically crashes within 2 to 3 seconds.
By proceeding quickly before the crash, I still manage to choose and set a ringtone.
It is well taken into account and run correctly with version 8.0.5beta7, but with version 7.4.22 the set ringtone does not work.

Thank you very much,now it works fine by disabling this option.

Hello Orux,

Thank you very much, it would indeed be very useful, not to say essential, to be able to work with the old strategy when using multi-tile maps such as IGN France maps, and I practically only use this type of maps for my hikes.
Because I would really like to be able to use the latest version of Oruxmaps which has some very interesting improvements,
And without this option it is impossible to examine in detail a road wich  straddles two adjacent tiles!

Regards...

Hello Orux...
I have used IGN maps of France at 1:25000  in .rmap format (many tiles) for a very long time, and the vector map of France in .map format,  so far without any problems (i have only these off-line maps in the map directory).
But with 7.5.9 beta 43, and now whith 8.0.3 GP, i discovered a problem that arises when i want to drag the current tile which is displayed (in an IGN map), to pass on the adjacent tile (in fact when the center of the map, pass in the adjacent map)
If the sliding is done very quickly, there is no problem, but if i slide more slowly, when passing to the adjacent tile, the current tile freezes becoming blurred, and i manage to slide but very difficulty to the adjacent tile, also blurred and which must be cropped whith zoom action.
Some times, according the direction of the sliding, the adjacent tile does not appear but the map changes  to vectorial (the only second map present in the map directory), even though the adjacent tile exists, since it can be displayed if i slide very quickly.
This fact is very annoying when i want to look a route wich  stradddles two adjacent maps

In this case, i must use version 7.4.22 again, which does not pose any problem in the same manipulation.

Best regards.

Hello Orux...
I have used IGN maps of France at 1:25000  in .rmap format for a very long time, and the vector map of France in .map format,  so far without any problems (only off-line maps in the map directory). But with 7.5.9 beta 43, 41, 39 (and maybe also the previous ones , but I don't have any more to try), i just discovered a problem that arises when i want to drag the current tile which is displayed from an IGN map, to pass on the adjacent tile.
If the sliding is done very quickly, there is no problem, but if i slide more slowly, in the direction down or to the right, when passing to the adjacent tile, the current tile freezes becoming blurred, and i manage to slide but very difficult to the adjacent tile, also blurred and must be cropped.
And if i slide to the left, the adjacent tile does not appear but the map changes to go to vectorial (2nd map present in the map directory), while the adjacent tile exists, since it can be displayed if i slide very quickly.
So I have to use version 7.4.22 again, which does not pose any problem in the same manipulation.

Best regards.

I tried the beta10 this morning and I found that when we stop the recording for a moment and then we want to continue the recording of the active trace, registration is not done.

The rest of the trace does not appear on the screen and is not saved in the database.

I do not know if this problem existed in beta 9

 

Hello!



Can you reproduce that problem?



When you restart recording the track, what option do you select (new track/new segment/continue current segment)?





orux

This problem come only with the option "Continue current segment", the 2 other options are OK.

I tried the beta10 this morning and I found that when we stop the recording for a moment and then we want to continue the recording of the active trace, registration is not done.

The rest of the trace does not appear on the screen and is not saved in the database.

I do not know if this problem existed in beta 9

 

It would be interesting and very useful to be able to choose, by a checkbox, to announce or not the seconds in travel time, because for hiking, the announcement of the seconds is completely useless, it unnecessarily overload the voice announcements !

This would focus on the information chosen and really useful.

 

Hello, I confirm the error with the first launch of Oruxmaps, whose exact wording is:

"Binary XML file line #2: Error inflating class PreferenceScreen"

Bonjour,

Je participe à OruxMaps en mettant à jour régulièrement les termes français des menus de l'application, j'ai pour cela le droit d'accès aux tableaux des langues.

Informaticien de métier, je ne suis cependant pas expert en cartographie et/ou en navigation, mais si vous connaissez bien ce domaine et si avez noté des erreurs, je suis tout à votre écoute pour les comprendre et les corriger.



Cordialement...

This is normal, it's not a bug !

long-press is a function made to move the waypoint, that's why it moves so as not to be hidden by the finger.

It's verry useful to correct the position of the waypoint

Try to move it to see...!

Of course, this function run only for the tracks in database and not for the KML tracks.

Je t'ai répondu en MP sur ce point.

Cela existe aussi avec Orux dans les propriétés des waypoints que l'on peut placer où on veut. On peut faire annoncer les distances (ex: à 80m tournez à droite), du texte TTS (nom du waypoint), des annonces vocales enregistrées, etc.... C'est ce que j'utilise en permanence !

It would be interesting to be able to choose whether or not to announce the seconds in the TTS messages.

Because during pedestrian excursions, the announcement of the second is useless and even annoying for the good understanding.

You can not associate waypoints created on OM, with a KML or GPX file.



If you want to associate waypoints created with OM on a route created with another application (GPX or KML file), you must first import this KML ou GPX route into the OM database.

Then load the route (manage tracks/routes), using the "continue recording the track" option. The waypoints created then will be associated with this route.