Thread: UX Request: Primo Currently Recording Track Displayed On Top

Looks like NNG themselves aren't interested in this issue either.

The exchange below takes place over several months, beginning in July 2024.

My query:

It's been a month since contacting NNG via the website and I've had no contact from NNG with regards to this issue.
I do not consider the issue closed and resolved, it is still ongoing.
It effects Primo on my Navig8r P50-PRO, and it appears the same issue is present in all Primo software for both WindowCE and Android devices.

All other GPS devices with varying software I've had over the years, including iGO8, have always display the currently recording track log ON TOP of other tracks, and on top of map features like roads, tracks etc..
This currently recording track log can also be referred to as a 'breadcrumb trail'.

How do I set my Primo on my Navig8r P50-PRO device to show the currently recording track log on top of other tracks, roads, streets and other map features?

Thank you

Their reply:

Thank you for your inquiry and we are sorry for our delayed reply.
We regret to hear that you are facing this situation.

For further investigation, please send us photos of the issue and about the tracklog settings of the navigation device: "Menu - More... - Settings - Trip Monitor".

Please also send us the "license" folder of the navigation device in compressed format:

1. To do this, please connect the navigation device with a USB cable to your computer
2. Select My Computer, and open the navigation device as a removable drive or disk
3. Find the "license" folder on the following file path on the navigation device: "/MobileNavigator/license"
4. Now right-click on the "license" folder, and choose "Send To - Compressed (zipped) Folder". Your computer will make a compressed file called "license.zip"
5. Please attach this file to your reply and send it back

Thank you for your cooperation.
Best regards,

I sent them the required photos, licence etc..

Their reply:

Thank you for the files.

The device model and the software that you have on it aren't under development any more.

However, we will ask internally if there is anything that you can do on your end to modify this.

We ask for your patience in the meantime.

Best regards,

Me again:

Thanks for the reply.

It is not only the Primo software on my device that has this issue, it seems to occur with any version of Primo on WindowsCE or Android that I have seen.
The exception being Nextgen, I have not seen or used Nextgen at all.

I await the solution patiently.

Thanks

Their reply, 6 months after I sent the above message:

We appreciate your kind patience. Our testing team has reviewed the issue, and I am afraid that this behavior is intentional by default and not configurable within the Primo software version.

We have forwarded your feedback to our product team, but unfortunately, there is very little chance that this will change in the near future.

Thank you again for your understanding and patience. Please let us know if we can assist you with anything else.

Best regards,

My response to that:

Thank you for the reply.

I understand that the version of Primo I have is an old one and no further resources will be used for improving it.

Is there a newer Primo software version I can purchase in which this behaviour is not intentional by default?

Thank you

And today their final response:

Unfortunately, to the best of our knowledge, this behavior is the default in all Primo versions, and there is no option to modify it. We understand that this may not be ideal, and we are sorry for any inconvenience it may cause.
If you have any further questions or need additional assistance, please feel free to reach out.
Best regards,

Very disappointing for a company that creates such good software to, in my opinion, go backwards by taking something that worked well and as expected in older software versions (iGO8 etc.) and deliberately breaking it in all versions of Primo...

I'm surprised that they even deigned to answer you
Given that the software is now very old and they have no interests or income, it's no wonder they won't develop any add-ons.
And the main thing is that almost none of the skins and add-ons were even developed by NNG itself
In fact, if the internet community was not this strong and there were not this many enthusiasts with adequate knowledge, I think iGO for WinCE although it is extremely functional and usable would have died a long time ago.

Yes I am also surprised they answered me.
A few times over the years I've requested their help with legit devices/software and map updates etc. because each time their website instructions on how to update the maps wouldn't work, and each time I was completely ignored, they never responded once.

I had contacted them via their website about this track recording issue initially and after a week or two they got back to me saying something along the lines of "as you haven't contacted us again we will assume the issue is resolved and will close it", to which I responded with my first quote above.

As long as I can still get my hands on WinCE devices, which are still readily available on fleabay and similar places I will probably just continue to use iGO8.

Every now and then I get frustrated about not being able to figure it out and decide once again to try different things thinking perhaps I can stumble across a solution but always seem to fail.
Last time I tried about 6 months ago I had the idea to make the display of the previously recorded/saved track logs semi-transparent, thinking that I'd be able to see the currently recording track log through that transparency...no such luck.

While I was able to make the previously recorded/saved track logs show on the map as semi-transparent, the damn Primo software it seems 'reserves' any of the screen pixels where the previous saved tracks are displayed on the map.
I couldn't see the currently recording log through them at all, even if I made them fully transparent, the currently recording track only became visible when my current path varied from where a previously saved track was on the map.

A few months before that I tried converting all my saved tracks to .kml files and then using them as routes shown on the map.
There was a limit to how many points could be used for each route, too many and it wouldn't work.
I was able to split them up and make a separate route for each lot of tracks in each area I needed them for.

This actually did work and the currently recording track log was displayed on top of the displayed route as desired.
It would only work with Primo's route settings set to 'Onroad', which wasn't a problem as I don't use a street map in either Primo or iGO8, only the basemap.
However it had one issue that annoyed me that I also couldn't solve, there was always a straight line shown from my current position to the first point of the route that unfortunately followed me everywhere I went and always pointed back to the first point at the beginning of the route.

Thank you, I shall try that when I get the time
That also explains why it was always showing the line towards what I believed was the start of the route, from memory I think I had to 'close' the .kml route or it wouldn't work, so at the time I think I ended up with the first and last route points at the same location.