That's true. I have tried that, but found that it did in some cases
not replace looking at things on real devices and under real light
conditions (like in a car, or in direct sunlight etc.)
It is a valid way of finding coding errors (but they are not a big
issue any more, the renderer is fairly stable now). So a good deal of
the trouble was finding color shades which looked conventional, and
where useful under as many conditions as possible. I was quite
surprised how different contrast or colors can look on different
devices!
On 31 Mai, 17:35, Jindřich Makovička <
makov...@gmail.com> wrote:
> I don't know your modus operandi, but a script that renders a bunch of
> .PNG images with given map coordinates and pixel sizes could simplify
> the testing a lot, and I think it's doable with OsmAnd's command line
> renderer.
>
>
>
>
>
> On Thu, May 31, 2012 at 5:23 PM, Hardy <
hm.gglm...@googlemail.com> wrote:
> > It's not really worth it for me ... :-)
>
> > I test each renderer change I make on 3 different Android devices with
> > different screen sizes and resolutions, and use a set of some 50
> > geologically interesting spots around the world (beaches, fragemented
> > coastlines, swamps, glacier, high density cities, mountain ranges,
> > areas with lots of bridges and tunnels, etc.).
>
> > So I do not really want to maintain my testing environment (together
> > with all the maps is takes) an yet another device ... :-)
>
> > On 28 Mai, 22:36, Victor Shcherb <
victor.shch...@gmail.com> wrote:
> >> Now you can test changes in default.render.xml directly on PC! Here are
> >> native libs thta you need to specify in Settings.
> >> On windows :
http://download.osmand.net/resource/cygwin1.dllhttp://download.osmand...
> Jindøich Makovièka- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -