In the help file it lists 335 pushpin symbols.
If I try and set a pushpin symbol to anything greater than 85 it crashes.
If I set it to something less than 85 it assigns a different symbol to the
one listed in the help file. E.g. 8 used to be some black pin symbol, but
now appears to be a strange car symbol.
What's going on?
Thanks,
Chris
Chris,
You may need to download, and then import additional pushpins. MapPoint 2009
comes with fewer pushpins, but the help file still contains the older info.
Download link:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9ab772c5-4d03-4f5e-a4e7-9fea604c0dee&DisplayLang=en
---
Marvin Hlavac
Laptop GPS World
http://www.laptopgpsworld.com/
.
This download only contains the 256 symbols that were in MapPoint 2002.. more discussion about this lots of places
http://www.mapforums.com/blogs/winwaed/47-adding-mappoint-2006-pushpins-mappoint-2009.html
http://www.mapforums.com/i-want-my-mappoint-icons-back-8339.html
I've changed my program to import them as custom pushpins each time.
Thanks,
Chris
"Eric Frost - MVP" <eric DOT frost AT mp2kmag DOT com> wrote in message
news:%23zzEduS...@TK2MSFTNGP03.phx.gbl...
if you don't mind me asking, how do you programmatically import custom
symbols?
I need to do that as well.
Thanks,
Alex. M.
I make sure I have bitmaps of the pushpins I want to use in a Bitmaps folder
off my application folder. Then I do something like this...
' Module Level
Dim RedSymbolIDsArray(1 To 20) As Integer
' Form Load
Dim objSym As MapPointCtl.Symbol
Dim objSymbols As MapPointCtl.Symbols
Dim I As Integer
Set objSymbols = objMap.Symbols
For I = 1 To 20
Set objSym = objSymbols.Add(App.Path & "\Bitmaps\Red" & I & ".bmp")
RedSymbolIDsArray(I) = objSym.ID
Next I
Then later I set a puspin to one of my red numbered icons (1 to 20). E.g.
objPin.Symbol = RedSymbolIDsArray(5)
Thanks,
Chris
"Alexander Manea" <Alexander Ma...@discussions.microsoft.com> wrote in
message news:9D88ECF2-719B-4B10...@microsoft.com...
Eric
"MeliDe" <Mel...@discussions.microsoft.com> wrote in message news:CCBD258D-0065-48E6...@microsoft.com...
I will use the workaround that has been kindly supplied in this thread but
it does annoy me that instead of leaving the previous 255 symbols intact and
adding new ones to them, and therby extending functionality, they have
reduced the functionality and made everyone change their code ! Oh well,
same old Microsoft....