New beta 11.x version

[Tronpo]

Hi Orux,

I have noticed an issue in the track manager related to handling files that contain only waypoints. I know this is not the ideal use case, but I use the track manager as a kind of database to organize files made up of multiple points, which I later load as overlays.

• Issue observed
When selecting two point-only files and using the "Join tracks" tool, if I choose to name the resulting file, that name is *not* respected when the new file is created. 
However, when performing the same operation with files that contain segments, the predefined name *is* applied correctly.

• Simple solution
Allow the track manager to handle point-only files in the same way it handles segment files, ensuring consistent behavior in all cases.

• More complete solution (proposal)
Create an alternative database, something like a **"layer manager"**, where both segment files and point files can be managed, and which acts as a staging area before loading them as overlays. 
This would provide a clearer and more specific workflow for these types of files.

• Current behavior that may confuse users
The track manager currently allows loading **dynamic (online) KML files**. 
These files do not contain points or geometries—only a URL—so they should *not* be loadable through the track manager. 
When trying to use them as overlays, they do not work, which can confuse users.

It is important to note that these dynamic KML files *do* work correctly when loaded directly from Android into the map viewer. 
For this reason, if a future **layer manager** is implemented, it *should* support managing these online KML files.

I hope I have explained this clearly.

Regards!

[Tronpo]

Hello Orux!! When I have a track loaded in the map viewer pulse on it the segment option menu opens, within the quick editing options, the function to change the thickness does not work. On the other hand, if it is loaded as a layer, if it works, the thickness change as a quick editing. Greetings

[orux]

Hello!

New beta, with some updates. I'll try to look into the latest things you've mentioned since my last post these past few days.


orux

[tof]

Hello everyone,

Quick question: I went for a ride using a GPX file with route tracking and the option to track uphill segments enabled. Everything worked perfectly until I took a detour of a few kilometers. The app then calculated a new route, probably using Brouter, but once I was back on the main road, the uphill segments no longer appeared. Did I configure something incorrectly? Should I disable the automatic route search option, or is it mandatory to always follow the GPX file since the app knows the exact number of uphill segments? Thanks in advance.

Best regards.

[Tronpo]

[cita autor=tof enlace=msg=60249 fecha=1772309496] Hola a todos, Pregunta rápida: Fui a dar un paseo usando un archivo GPX con seguimiento de rutas y la opción de rastrear segmentos cuesta arriba habilitada. Todo funcionó perfectamente hasta que tomé un desvío de unos pocos kilómetros. La aplicación luego calculó una nueva ruta, probablemente usando Brouter, pero una vez que volví a la carretera principal, los segmentos cuesta arriba ya no aparecían. ¿Configré algo incorrectamente? ¿Debería deshabilitar la opción de búsqueda automática de rutas, o es obligatorio seguir siempre el archivo GPX, ya que la aplicación conoce el número exacto de segmentos ascendentes? Gracias de antemano. Saludos cordiales. [/cita]

Hello, according to my experience the app also calculates the climber setches for the new route created, it is possible that these new climber setches do not exactly coincide with the setches of the original route. It is possible that when returning to the main route he did not recognise it as such, that is, he did not use this data to give the route tracking notices. I haven't been able to verify this new version yet.

[orux]

Hello!

Beta version updated, thanks!


orux

[Tronpo]

Hello!

Beta version updated, thanks!


orux

Hello Orux!! Checked the update of the libraries, now in mapsforge the complex symbols such as osmc are correctly represented in topics like Elevate👍🏻, regarding the shading of hills for vtm it generates a doubt, would a new configuration be necessary in the app? When you turn on mapsforge shading in the app settings, no shading is shown in the vtm viewer. I made a mistake when quoting as a change in these libraries the implementation was earlier you can see it here https://github.com/mapsforge/vtm/pull/1189

[Catdreamer]

Please also update the Traditional Chinese translation. Thank you!

It would be even better if the new or revised strings could be synchronized with each new release.

[kkolesar]

this is not something new (in betas) but I will post it anyway, if orux can see, what is the issue
 ... in tracks list I have many of them without thumbnail, despite of running command 'Reload track thumbnails ...' more times.
 

[Tronpo]

this is not something new (in betas) but I will post it anyway, if orux can see, what is the issue
 ... in tracks list I have many of them without thumbnail, despite of running command 'Reload track thumbnails ...' more times.
 

Hello, according to your capture, it seems rather that the app does not find the selected map to use it, since the route is seen and the thumbnail is created, does the selected map still exist in the app? You can try selecting another map for thumbnails, clearing cache, restarting the app, and forcing new thumbnails. Greetings troNpo

[kkolesar]

Hello, according to your capture, it seems rather that the app does not find the selected map to use it, since the route is seen and the thumbnail is created, does the selected map still exist in the app? You can try selecting another map for thumbnails, clearing cache, restarting the app, and forcing new thumbnails. Greetings troNpo

I changed map, cleared cache (all I know), restarted app - no success. and, it is even more wierd - if I go into properties of track without thumbnail and trigger refresh thumbnail command for that single track - voila, thumbnail is there ?!? ... so, there is some issue with bulk refresh anyway, I think.

[Tronpo]

Hola Orux!!
Cuando damos color personalizado a un campo de datos del cuadro de mando, parece que se colorean otros aleatoriamente sin ningún sentido ni voluntad.
Saludos

[kkolesar]

Three 'types' of thumbnails in list. Have no idea how this happens.

[orux]

I changed map, cleared cache (all I know), restarted app - no success. and, it is even more wierd - if I go into properties of track without thumbnail and trigger refresh thumbnail command for that single track - voila, thumbnail is there ?!? ... so, there is some issue with bulk refresh anyway, I think.

Hello!

Refreshing the main list only regenerates thumbnails for tracks that don't have them. On each individual track's screen, it does force the creation of a new thumbnail.

The thumbnails you see with a black background are because the online map you're using is problematic; it's returning empty tiles.

When you refresh from the main list, those black thumbnails don't update because they already exist; the app doesn't recognize that they have no background.

I'll look into adding an option to force the creation of new thumbnails from the main list.


orux

[kkolesar]

I have OpenstreetMap for thumbnails and sometimes thumbnail is created, sometimes it isn't. it's nothing important for general use of app, I just wanted to provide some information about this for your knowledge.