Hi Felix, loads of text. Ok, let's start:
> > 1. > Qlandkarte draws blue points instead of a POI symbol. This is really > ugly. All POI for my maps have symbols in the .TYP-file for every POI > type present in my maps, so this really should not happen. And if a POI QLGT tries to fight the OSM poi clouds by reducing the icons to a small dot when they overlay. If you zoom in close enough to give each icon it's space all icons should be shown. > is invisible in the .TYPfile, well then Qlandkarte should accept that > too and not display it (those POI are only in map so they can be > searched, they are not intended to be shown). You are right QLGT is not aware of such a flag. My current sources of information do not know about such a flag. Probably because they are outdated, too. The problem is, that I am pretty tired of ripping each piece of information out of the binary data or out of the minds of those writing the typ file creators. If you tell me the location of that flag I can implement the stuff. > 2. Labels. > Qlandkarte does not respect the label size set in the .TYP-file. This is > there for a reason, so yes Qlandkarte should respect it too. Qlandkarte > maps get really crowded and disgusting due to displaying too many labels > (that are set to invisible in the TYP-file). Also it seems to me that Ah, yes the showLabel flag is evaluated badly. I fixed that. Let's see if I can motivate myself for the label size, too :) > > 3. Colors of lines and rendering of line bitmaps in curves. > Qlandkarte GT: vs MS: > > Notice that Mapsource as well as all modern Garmin GPS blur patterns > that are like x0x0x0 over the underlying color, this is nicer than what > Qlandkarte GT does (though not that important). Well, I just can do what the render engine of Qt allows me to do. You can select anti-aliasing. The current settings is the strongest possible. But if that does not look good enough I hardly know how to change. > Also Qlandkarte renders stuff too close on lines that are curvy, notice > that Qlandkarte shows many more arrows than Mapsource (in the above > example it is not even drastic, sometimes it is like 3-4 times of what > Mapsource shows). It takes the bitmap as defined and render it along the polyline. If the bitmap is 15 pixel wide it will be repeated every 15 pixel along the line. I can't tell if MS is optimizing that process for what ever reason or if it is just a happy glitch in their render engine. But I hardly would know how to change that concept to make everyone in every situation happy. > Especially 1. and 2. are especially annoying and make Qlandkarte > rendering of maps really ugly versus how Garmin renders the maps. 3. is > not so important. Cleaning up the OSM mess by moderating the senseless crowd of POIs would surely help, too. > P.S. if images are not sent through the list, then drop me a mail and I > will upload them somewhere and put a link. I had to push the mail. But that is ok. Oliver ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
