Hi Nick
> Without padding image is always rendered correctly, which seems to indicate
> that the alphas
> are parsed correctly?
Yes, remembered that I could test these ones out easily and I've now
changed the code to no-padding and it all looks good.
I'll commit it with that change now then.
T
Hi Steve
Have been experimenting with
w =odd L even
w =odd L odd
w sizes 3+
I used my bus bitmap to check as we've got 'millions' of bus stops in our
area.Use Mapsource
and my oregon to check .
Used padding as you suggested but image always appeared as noise - even
tried different lengths o
Hi Steve
Brilliant, have not had a chance to test this.
Interesting what you are saying about odd widths; never thought
about checking this with color mode 32
That makes sense; I've also not checked pois with width = odd and <16/ 8 /4
Will let you know
I've not as yet implemented saving n
Hi Nick
> But I can see the wisdom behind #cc11 and #cc when alpha=0
> I might change this in TYPWiz2 - thanx for the tip!
Great. You can also use the same format for the colours in the normal
pixmap format too, although I can see that you might not want to
change that for compatibility.
Hi Steve
You've certainly done some thinking about this;
I like the
DayXpm="4 4 0 1"
"#FFF5FF#FFF5FE#FF65FF#FF65FF"
as its visually more representative and takes up less space!
similarly with the rgbas
#cc11#0033#0066#0099"
I used 'alpha=' because of non truecolor colormode
Hi Nick
btw any progress on true color pois with colormode 32 - although in my
experience only Mapsource/Basecamp seem to render this type correctly.
I've now implemented colour modes 16 and 32 for the true colour
image type. As usual I ignore any ColorMode=N declaration and
determine the lowe
Hi Steve
I must have used an older mkgmap.Thanks for testing this again.
'The term 'Tag' may be non-standard or incorrect and I'd be glad to
replace the word with a more standard one'
I think Tag is clear enough.
btw any progress on true color pois with colormode 32 - although in my
experienc
Nick
> I meant that the error messages in the past were very helpful - particularly
> the line number refs - but for some may need to be explained more fully in
> a help file.
Oh OK, I missunderstood, sorry .
> Now I don't get any msgs eventhough the code may be incorrect, ie
This is strange
Steve
I meant that the error messages in the past were very helpful - particularly
the line number refs - but for some may need to be explained more fully in
a help file.
Now I don't get any msgs eventhough the code may be incorrect, ie
xpm="32 5 2 1"
"0 c #C0C0C0"
"1 c #00"
"123456
Hi
> Steve, some of your helpful error messages could perhaps benefit from some
> elucidation?
>
> expected $ but got ... etc
Are you sure that error still occurs? I changed a lot of them during
development. I don't see a message in the source with that form any
more.
I'm afraid you are going to
I thinks Steve's description of how to create polygons,lines and points as a
text file 'says it all'.
Perhaps what's missing is how to actually create a typ file as a command and
how to use the options discussed earlier.
Steve, some of your helpful error messages could perhaps benefit from some
el
> I think the wiki page about TYP files requires an update after Steve
> added the TYP compiler:
> http://wiki.openstreetmap.org/wiki/Mkgmap/help/TYP_files
>
> Anybody out there who knows how to work with the TYP feature and who is
> willing to update that page?
I did write a page describing the
Hi all,
I think the wiki page about TYP files requires an update after Steve
added the TYP compiler:
http://wiki.openstreetmap.org/wiki/Mkgmap/help/TYP_files
Anybody out there who knows how to work with the TYP feature and who is
willing to update that page?
Thanks!
WanMil
___
13 matches
Mail list logo
