WillT

Members
  • Content Count

    26
  • Joined

  • Last visited

  • Days Won

    1

WillT last won the day on December 31 2018

WillT had the most liked content!

Community Reputation

4

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well this has been a bunch of learning! Now that I know my way around PDN much better, a side benefit is that perhaps I will use it much more than I thought originally. Anyway I am hesitant to say this is figured out and possibly jinx it, but I do seem to have it working for this particular signpost image. I was doing some of the things @IHaveNoName suggested above. While working with a version of the file in .ico format, I decided to zoom way in and try adding solid black to some of the signpost pixels, and erasing completely the contents of the adjacent "transparent" pixels. This gave me clean edges, although it looked bad and boxy zoomed/enlarged like that. BUT, when I put it back to the 16X16 size I decided I wanted for this particular map symbol, it looked fine. So I saved it to the correct folder and it showed up in the BaseCamp software. Then I saved a version of the file to the Garmin GPSr and it worked, sort of. I could make a waypoint on the GPSr unit and assign it the signpost symbol file and it showed up. But when I sent a waypoint that had the signpost symbol already assigned to it in BaseCamp to the GPSr, it did not show the signpost, but rather the generic waypoint symbol blue flag. I realized that this was because even though the Garmin products could display the .ico files just fine, in order to have the symbols synced between garmin devices, the Garmin firmware/software was requiring them to be .bmp, not .ico.... And they had to have the exact correct names. (In this case, 002.bmp in BaseCamp and Custom 2.bmp on the GPS receiver so the Garmin software would know to use those two files interchangeably.) So.. what I did as the last step was open each of the .ico symbol files in PDN and just save them as .bmp files. PDN just seemed to save the .ico files as .bmp files without changing anything about the image or colors, etc. So now it works as it should. Now at least I know how to get a small symbol icon file from an image that has anti-aliasing already on it. BUT... I think I will really try to make my own files for the remaining symbols I need and avoid the issue from the start on as many of the symbols as possible. Thanks to everyone for all the suggestions along the way. It took a while and a lot of studying up on PDN by me to understand most of the suggestions, but I feel it was well worth it.
  2. So after doing the following steps, the black signpost image still has the magenta bleeding around the edges. (Looks pretty much the same as the previous images before using the plugin.) Started with the original downloaded image at 32X32. In PDN applied the Black and Alpha+ at the default setting to the one layer with the black signpost. Then created another layer and filled it with the bucket with 255,0,255 Swapped the position of the layers so the symbol looked correct. (Magenta background with black signpost.) Saved as .bmp file at 24 bit and flattened. Did I miss a step or use the plugin incorrectly or something?
  3. Oh wow! Thanks. I am on the west coast so earlier but time for me to call it for now too. I will try it once more and post the results and the exact steps I took to get there if it does not work. Whenever you get to look is fine but I won't get back to it until mid day tomorrow. I really do appreciate the help!
  4. Wow! Finally! That seemed to do it. The edges look a little fuzzy for some reason though but on something that small it is not the end of the world. What did you mean about the contrast? When and on what would that last step be done? Edit: I spoke too soon. I don't quite have it yet. Somehow I ended up with a solid white background instead of magenta/transparent. I'll do it again from scratch to see if I can figure out why.
  5. I have been trying all combinations with no success yet. So next I will leave the plugin as it is and apply it to the original layer with the signpost? Then create a second layer with the 255,0,255 fill?
  6. So I have the image done and when choosing the plugin it gives me this popup window. But I don't have a clue as to what I should have the sliders at unless it is just the same as when I create the 2nd layer, 255,0,255
  7. Yeah. And what I want to do, just making a few custom symbols to use in my maps seemed like it would be so easy!! Thanks! Got it installed and will try it. Makes sense. Thanks.
  8. Makes sense. Will the plugin you suggested still work even if the original image is anti-aliased?
  9. Ha! You are right, there is a lot I don't understand but slowly getting there I think, Interesting because in that example you posted, it looks to the uninformed eye that the top image that IS anti-aliased would work best to avoid the bleeding?
  10. Thanks I found it finally with the results posted right above. It made no difference to the final image quality. I am just now installing the plugin you suggested to try that.
  11. I just repeated the process with anti aliasing turned off as in the snippet below. It made no difference to the final version. Attached is the original 256X256 version of the file I started with.
  12. I thought the same, but I could not find anywhere else to follow the instructed suggestion of turning anti aliasing off. Where in PDN is that? On edit: Sorry, finally found it. Missed the tiny squiggly menu item.
  13. On this particular sign post, I just tried that as they have both a 16x16 and 32x32 png version available. So I got the 16x16 and opened it in PDN. Then with "Selection Clipping Mode" set to pixelated, I added the magenta layer. Then saved as a flattened .bmp into the Garmin folder. BaseCamp map uses it fine, but it looks exactly the same as the one I made reducing from 256x256 to 16x16. So starting with an already small image and skipping the reducing step did not matter.
  14. Thanks - That may indeed work for this symbol but many of the symbols are more complex in nature and design. Most of the 8 or 10 symbols I want to add to my maps are from free downloads, either websites or from people I have communicated with on other non graphic and non mappin sites. I just use what is available and am trying to make them work with the Garmin products. I am so close it is frustrating. I have it working except for this last edges part.
  15. I have been reading the help files, tutorials, etc. and not really getting anywhere on this specific problem. I am leaning a LOT about PDN that I will probably never need since really all I am trying to do is this one procedure. But I can not figure out how to make less of the magenta bleed around the symbols I am using. I thought maybe your suggestion to turn off anti aliasing would be an easy solution if it worked. The only place to do that I can find is in the selection clipping mode drop-down. So I changed it to pixelated but it really did not make much of a difference at all. Just for testing, I used a 256X256 .bmp of the same symbol and it looks great. Way too huge, but perfect. Once that image is reduced to 32x32 it bleeds the magenta like crazy. Frustrating.