Re: [mkgmap-dev] [Talk-de] continue statement and order of drawn ways?
Am 04.05.2011 00:08, schrieb Felix Hartmann:
On 04.05.2011 00:05, Henning Scholland wrote:
Am 03.05.2011 23:37, schrieb Felix Hartmann:
On 03.05.2011 23:27, Minko wrote:
Yes, that is also a good alternative, 0x01 as a transparent line and on top either 0x10f01 or 0x10f02
you cannot make a line transparent by omitting it from the typfile, but go ahead and do your tries.
Yes, but you can use a transparent png-file ;)
Henning
And then you have streetnames shown, but no street.... If you remove the streetnames on 0x01, you remove streetnames on the broken Oregon, edge 800, gpsmaps 62 series, for all maps (until hard reset)
The streetnames should be at 0x01, because this is rendered on top. 0x10f01 or 2 were rendered below and will be visible because of 0x01 is transparent. Henning
On 04.05.2011 00:41, Henning Scholland wrote:
Am 04.05.2011 00:08, schrieb Felix Hartmann:
On 04.05.2011 00:05, Henning Scholland wrote:
Am 03.05.2011 23:37, schrieb Felix Hartmann:
On 03.05.2011 23:27, Minko wrote:
Yes, that is also a good alternative, 0x01 as a transparent line and on top either 0x10f01 or 0x10f02
you cannot make a line transparent by omitting it from the typfile, but go ahead and do your tries.
Yes, but you can use a transparent png-file ;)
Henning
And then you have streetnames shown, but no street.... If you remove the streetnames on 0x01, you remove streetnames on the broken Oregon, edge 800, gpsmaps 62 series, for all maps (until hard reset)
The streetnames should be at 0x01, because this is rendered on top. 0x10f01 or 2 were rendered below and will be visible because of 0x01 is transparent.
Henning
What is rendered on top and what not depends on GPS Firmware. For old GPS it is opposite to Mapsource 6.16 if you use a .TYPfile. If you omit entries from typfile, it changes order. There are quite a lot of variables, and in general stuff on top of each other is stupid. Better use transparency wisely, it's much more powerful than layers or top/down drawings, and it works consitstent on all GPS except Zumo (all that is all that are able to use .TYP-files).
Maybe the word 'transparent' is a bit confusing. With transparent I don't mean to omit line type 0x01 from the typ files at all. Like Henning said, you have to use a bitmap pattern without colours (=transparent) in the TYP file. On top of this, you use another bitmap with an arrow in the middle, for highways with oneway. This has to be a non routable line to avoid problems. For highways without oneway, you use another line type with a solid colour. This isn't stupid, it works, only if you know what you are doing.
Minko (ligfietser@online.nl) wrote:
Maybe the word 'transparent' is a bit confusing. With transparent I don't mean to omit line type 0x01 from the typ files at all. Like Henning said, you have to use a bitmap pattern without colours (=transparent) in the TYP file. On top of this, you use another bitmap with an arrow in the middle, for highways with oneway. This has to be a non routable line to avoid problems. For highways without oneway, you use another line type with a solid colour.
This isn't stupid, it works, only if you know what you are doing.
The only thing to watch out for is what your GPS uses when it pops up a routing instruction. On mine, it shows the routeable lines. When I set routeable lines as transparent in the TYP file, then the GPS ignores the transparency and used a 1px grey line instead, which was a bit confusing. It would be even worse if it just displayed the roads transparently as the routing instruction would just show a routing arrow, and no roads. In the end, I set the routeable way as a thinner version of the "display" road, using the same colouring. This way, when browsing the map you see the display road (because it's wider), but when the routing instruction pops up you see road styles that correspond to the overall map style, rather than thin grey lines. -- Charlie
participants (4)
-
charlieï¼ cferrero.net -
Felix Hartmann -
Henning Scholland -
Minko