[GRASS-dev] maybe bugs

[Martin Wegmann]

On Thursday 27 July 2006 14:29, Maciej Sieczka wrote:
> Martin Wegmann napisa?(a):
> > well, perhaps I missed a part but doing the steps:
> >
> > g.region save=africa
> > d.zoom
> > g.region africa
> > I get a small subset somewhere in the middle of Africa
> > (what is as well the region I get with r.patch see below->)
>
> Maybe this explains: gis.m doesn't read nor write to the WIND file,
> while d.zoom/g.region do. What you change with d.zoom/g.region will not
> affect gis.m display (unless you press 'Zoom to current region' from
> gis.m menu) and vice versa: if you zoom/pan in the gis.m canvas it will 
> not affect WIND file, ie. current region settings. Check with g.region
> -p for yourself.

it means, if I zoom into a region with gis.m and say 'g.region save=XX' in the 
CLI and afterwards "zoom to .. region" it won't work - I tried it - well it 
does not make sense for me who is working on the CLI and GUI.

How do I define a new region, if gis.m and g.region does not talk to each 
other? Everytime starting d.mon x0 - d.rast XX - d.zoom - g.region save=XY 
and then it works in gis.m as well or is there a "gis.m-way"

sorry, if I misunderstood you but I am a bit confused about g.region/d.zoom 
vs. gis.m. 

>
> >>> 3)
> >>> zoom out in monitor makes the display window smaller and smaller - this
> >>> bug has been reported before and I thought it would have been fixed
> >>
> >> I don't understand. Can you elaborate?
> >
> > try:
> >
> > zoom into map
> > zoom out: very elongated rectangle
> > map becomes smaller but is squeezed to one border (depending of the
> > orientation of the elongated rectangle)
>
> gis.m or d.m (d.zoom)?

gis.m with the included zoom function in the monitor

>
> If d.m, it behaves exactly the same as d.zoom and there's nothing there
> could be done about it.
>
> In of gis.m you have drawing modes:
> Constrain map to region geometry
> Map filles display window
>
> The first mode behaves pretty much like d.zoom (only it doesn't modify
> WIND file), the latter is maybe what you are looking for.
>
> Does that explain?

thanks, now I found the buttons on the right hand side - ,-)

well but it does not explain why the visible extend (white space vs. grey 
background) becomes smaller and smaller (by zooming out with very elongated 
rectangle) when selecting "constrain map to region geometry", does it?

>
> >>> 4)
> >>> r.patch does not patch two raster but parts of the first raster with
> >>> adjacent parts of the second one - can somebody report the same
> >>> behaviour?
> >>
> >> Please provide a test case explaining what's wrong and what's expected.
> >> Or maybe you forgot that r.patch is region sensitive?
> >
> > well, I think as long as I haven't solved the g.region problem r.patch
> > might as well be restricted to the region settings.
> >
> >
> > hmm, I restarted the whole GRASS session and now it (g.region, r.patch
> > only) works, something must have looked the g.region settings. I try to
> > reproduce this behaviour, but I have no idea what causes g.region to
> > unconsider the new g.region settings. I'll mail if I found out.
>
> I suppose this is all your missundersting of region handling in gis.m.

hmm, probably, thanks so far; I think I have to become more accustomed to 
gis.m. 

have a nice evening, Martin