GeePeeEx Editor questions

If you move to another computer, you just email Phil for a new code. I moved my GeePeeEx from my desktop to my laptop since I actually use my laptop far more often than my older desktop.

Well, we're better off waiting for the official answer from Phil, but I *think* it's because POILoader 2.52 resolved a work-around that he had to do with older versions of POILoader. Selecting the device may no longer be required with 2.52.

I've never used these options, so I can't help you with this one.

I get that occasionally too, and I think this is a compatibility issue for different models of Nuvi.

As for the alpha-sorting, I've not noticed this nor tried to sort the files, since they display on the Nuvi in distance order anyway.

I only started using the latest version 1.8.1 a very short while ago and I'm pretty sure that's when ghosting out the "select Nuvi model" was first ghosted out. Haven't noticed any changes because of that, however.

These are just parts of the Visual Basic run-time and associated Active-X controls (Treeview, WebBrowser control etc) - ie they're all standard Microsoft re-distributables; nothing related to the GeePeeEx licencing code.

For obvious reasons, I won't go into the details - but yes, the Activation Code is tied to the hardware. This shouldn't be a problem though - just let me know of any changes and I'll gladly re-issue the code.

Before dealing with your other issues; a bit of background for you:-

Prior to version V2.5.2, POILoader didn't provide access to all fields within the resulting .GPI file. Although Garmin seem to have tested their units with fully populated .GPI files (presumably created by 'other' software), there were MAJOR differences in the way that different units responded to these partially initialised .GPIs.

One of the most obvious 'partial' .GPI, is one created from .CSV input (only 4 parameters). Every unit is able to display these files (with some subtle, but non-fatal differences). However, exploring the other fields, using .GPX input, gave results that varied wildly, depending on the unit in question.

It was because of this, that I added the "Target Device?" question (and associated processing) to GeePeeEx Editor. It applied a variety of device-specific kludges to overcome these foibles - with an unfortunate side-effect that the .GPX files were not easy to share. That was the reasoning for the "Plain Vanilla" file type. Although such files didn't display properly on ANY Garmin unit, the data was intact and fully complied with the GPX standard. They were intended really for use by non-Garmin software.

When I added supported for POILoader V2.5.2, the main goal, was to get rid of the need for that "Target Device?" question. There are still differences, but I took the stance that a few glitches could be tolerated, if that goal could be largely achieved. Your "." padding issue is one of these, and there is another related to the display of address fields that have the 'country' field filled in. It is also the rationale behind the decision not to provide separate access to the <cmt> and <desc> fields.

In the next version, I will probably remove support for POILoader V2.4.2 - and (things like the right-click 'remove device-specific formatting' options). The "." padding feature can be sorted out at the same time.

It is interesting to note, that in your experiments, you chose Nüvi 7xx as the closest match for the Nüvi 8xx. In fact, I think Nüvi 3xx is probably nearer the mark! Someone recently sent me some screen shots and it was surprising to see the 'single page' display again .. ie there is no "MORE" button, as in the majority of the other units.

We may have to run through some detailed tests to see exactly how this device responds, compared with the others. For now, it would be useful if you could confirm that you are in fact, using the latest version of POILoader (ie V2.5.2).

As a starting point, how does my example file
http://GeePeeEx.com/StonePages.gpi display on the 850?

1st, thanks for the imput johnc. Of course you're right about the alpha sorting...they're going to display on the nuvi in order of distance, not alphabetically, regardless of how they're sorted in the gpx file. DUH! I think my brain shut down at that point, trying to sort all this out for hours at a time.

Hornbyp....thanks for the detailed background info. That gives me a little better understanding of what's going on, such as the Target Device selection not being applicable with POILoader v2.5.2 (which I am using) & why the periods are randomly appearing in the names. However, I'm confused why you're surprised I chose the nuvi 7xx preview mode (instead of 3xx) to preview the text. Since using the Target Device selection doesn't apply to POILoader v2.5.2, the output gpx file is the same, regardless of which preview mode I used, isn't it? Like you stated, the "MORE" button is absent in the 3xx mode & does appear in the 7xx mode, but that doesn't translate to the output file when it's loaded on a nuvi 850....because there's no selection available with the Target Device button. Or is there something else I'm not understanding?

I still can't figure out one last problem that I mentioned above...that is, I'm still getting some truncated description fields. fx, one of of my test gpx files I made has approx. 100-125 characters, yet only displays 51 characters on my nuvi. I'm not sure at this point whether it's a bug pertaining to the nuvi 800 series, or I'm just doing something dumb (again).

To answer your last 2 specific questions:

1) yes, I'm definately using POILoader v2.5.2.

2) I loaded your test StonePages gpi and everything seems to work properly, other than the random periods that you've already explained. Text displays as it should & audio is fine.

I misunderstood ... I didn't know you were referring to the 'preview'. That's another topic that needs addressing :sigh:

Yes.

No - you're right.

Hopefully then, this is going to be something simple. Can you send me some screenshots and your .gpx file?
(If you could also send me some screenshots of one of the entries from the 'Stonepages' sample (in its entirety), I can use it to add a proper 8xx Preview mode.)

email me at: g p x @ h o r n b y . m e . u k

All that being said, I would like the option to sort the list myself. Prior to buying a 760 with Routes capability, I was using multiple waypoints to provide some functionality of forcing a route. I would add a Stop# to the POI names like:
1-First Waypoint
2-Point on Scenic road
3-Next Scenic road
4-Town to pass through
5-Final Destination
It would be easier to mentally arrange and picture the "route" if they were in order while editing. And the numbers in the name would help remind one of the intended order because once loaded to the Nuvi they would sort by distance. Most of the time the 'by distance' would probably work fine, unless you were trying to build a circuitous route.
Reading of all the subtle and not-so-subtle differences of how each unit displays GPX files, I'm absolutely amazed that Phil can keep his sanity while trying to maintain a compatible output for standards that are different on each model.

Phil,
Any thoughts or news yet about the formatting problems with the nuvi 8x series?

I got the file you sent (thanks!).

It's on my list of "things to do"

I replied by email, but in case you didn't get it:-

It's a bit confusing - the screenshots you sent clearly show a "MORE" button. Yet, I was sent some by an Italian 8xx user that definitely shows it using "scroll arrows" instead...
It was also not interpreting html markup.

I'm not up to speed on the 8xx firmware versions - but I know there was a version released recently. Has this affected anything?

Nope, sorry to say Phil, but the screens still display the same as the screenshots I sent you. I just updated to the latest firmware today.

I've been doing some more tests...

Can you confirm, which version was that - V3.20?