Hi Felix,
Thanks for the response. I am just getting started on my debugging and,
in fact, one of the things I was going to try was changing the POI
"types". I will let you know how it goes.
Regarding line "types", I generate custom line types and supply the line
pattern as opposed to using any of the well-known types. Maybe this
could be a work-around for you? I could supply examples for you, if needed.
The whole visibility of objects at different zoom levels has always been
a challenge and is very device dependent, unfortunately. For what I do,
I generally don't run into it too much (because I don't generate
references to device-internal icons, etc.). As a whole, Garmin's UI and
compatibility between devices is terrible and unfortunate. I think it
stems for poor design decisions, limited memory, etc. I've worked at
software companies for 4 decades (as a developer) and I've seen this
kind of sloppy design and poor management. It is what it is and someday
the phones will eclipse all this poor hardware and software.
I saw you registered at my website. Please watch the (poor and
outdated) videos and try it out. Let me know if you need any help and I
am always willing to share all that I have.
Oh, I just received a Tread and it also does not display the text for a
"POI" type. I will start debugging now...
Best of luck on your project.
Scott
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
