Moritz Lennert wrote: > > Another potentially disruptive update: the raster library now uses > > floating point values for coordinates. > > > > Please help test d.* modules. With 120 modified files, the chances > > that I managed to break something are relatively high. > > There seems to be a problem with d.vect. Area fill varies according to > zoom level. When you display an entire map (e.g. census_wake2000 in the > NC demo data set), a lot of areas are not filled, and there are empty > spaces between areas. Zooming in reduces the non-filled and empty areas > until they seem to disappear when you zoom in really far.
I'll try to look into that later (the NC data set is 135MiB). Does changing the render= option have any effect? I changed the default from render=c to render=l, so this may suggest a bug in that particular rendering mode (l should be more efficient, but it had problems with XDRIVER). -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
