| View previous topic :: View next topic |
| Author |
Message |
MaFt
Pocket GPS Staff
Joined: Aug 31, 2005
Posts: 15130
Location: Bradford, West Yorkshire
|
 Posted: Mon Apr 17, 2017 1:42 pm Post subject: |
 |
|
| Kremmen wrote: | | And if you can crack the correct shade of purple, like my new camera iconc borders, they can be totally invisible. |
I think it's officially magenta that gets converted to being transparent. in hex it'd be ff00ff (full red and full blue, no green) and in RGB: 255,0,255
That might help you create the colour in your graphics software
MaFt |
|
| Back to top |
|
 |
MaFt
Pocket GPS Staff
Joined: Aug 31, 2005
Posts: 15130
Location: Bradford, West Yorkshire
|
| Posted: Mon Apr 17, 2017 1:48 pm Post subject: |
|
|
@ Metblackrat - sorry, didn't realise you'd already posted the info re magenta.
@ pcaouolte - is this from one of our POI files? |
|
| Back to top |
|
|
Kremmen
Pocket GPS Verifier
Joined: Mar 03, 2006
Posts: 7039
Location: Reading
|
| Posted: Mon Apr 17, 2017 3:09 pm Post subject: |
|
|
| MaFt wrote: | | Kremmen wrote: | | And if you can crack the correct shade of purple, like my new camera iconc borders, they can be totally invisible. |
I think it's officially magenta that gets converted to being transparent. in hex it'd be ff00ff (full red and full blue, no green) and in RGB: 255,0,255
That might help you create the colour in your graphics software
MaFt |
Trev and I did that, 255,0,255, but M$ Paint, by default, saved it in the wrong bit format so it displayed as magenta. Dragged it into PSP, changed the RGB bit level and it worked first time.
Can't remember off hand what it was and what I changed it to.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
 |
|
| Back to top |
|
|
pcaouolte
Frequent Visitor
Joined: Dec 27, 2006
Posts: 998
Location: South Lincs, UK.
|
| Posted: Mon Apr 17, 2017 4:50 pm Post subject: |
|
|
| MaFt wrote: | | @ pcaouolte - is this from one of our POI files? |
No, the POI files from this site do not have the problem, they are correct when downloaded.
| Privateer wrote: | | Instead of using a hex editor, would using Notepad or Notepad++ to load and then save the .csv file work to strip those bytes? |
Using Notepad and re-saving the file leaves the troublesome bytes intact. I don't have Notepad++. Using Excel and re-saving deletes the troublesome bytes.
I don't know how I got the unwanted bytes in the first place. The files would have been converted from OV2 to CSV when I moved from TomTom to Garmin but I can't remember which utility I used to do the conversion. The bytes don't seem to cause a problem to other software but POILoader doesn't like them.
_________________
Paul |
|
| Back to top |
|
|
Kremmen
Pocket GPS Verifier
Joined: Mar 03, 2006
Posts: 7039
Location: Reading
|
| Posted: Mon Apr 17, 2017 5:06 pm Post subject: |
|
|
Ah
OV2 to CSV was the same problem I had. I used Notepad++ and that helped because you could see the offending characters.
_________________
Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
|
|
| Back to top |
|
|
MaFt
Pocket GPS Staff
Joined: Aug 31, 2005
Posts: 15130
Location: Bradford, West Yorkshire
|
|
| Back to top |
|
|
|
![]() Posted: Today Post subject: Pocket GPS Advertising |
|
|
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
|
|
| Back to top |
|
|
|
Forum FAQ
Search
Usergroups
Profile
Log in for private messages
Log in
