Thanks for the nice reading,<br><br>1 - Working with many layers is rather painful in GRASS right now.<br><br>An idea might be that when r.in.gdal a multi-layer image, it automatically creates one multi-layer virtual access (group?) in the GUI.
<br>Another idea might be that user may define (interactively select, or even automagically scanned for in the list) a rootname and all layers in the mapset answering to the "$rootname"+"*" would be grouped as one to the user.
<br><br>2 - About screen display of large images, high-resolution images (and g.region/zoom mis-haps) may cause great frustration to users while waiting to redraw.<br><br>Maybe there is a way to fasten this. A very low resolution (about screen size, something like a fat thumbnail) layer could be accessed initially. Or even a set of pyramid layers (?).
<br><br>3 - The focus on display is an important concept for users.<br><br>While running the lab sessions, newbie students only hang GRASS because they do not know that you have to right-click to quit. They close the tool dialog box, sometimes the active window too, and go to another task. This comes certainly from other software experience, maybe when the mouse goes off active display for some time, then the tool can be put in "hibernation" or inactivated, not sure how/what, so that GRASS can still do other things.
<br><br>Yann<br><br><div><span class="gmail_quote">On 11/6/05, <b class="gmail_sendername">Maciek Sieczka</b> <<a href="mailto:werchowyna@epf.pl">werchowyna@epf.pl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The 'active' box idea is nice. And I think it should be set to 'off' by<br>default. Otherwise adding heavy raster layers, or vector layers with<br>many objects, would be slow, as each layer would have to be drawn first,<br>
as currently Grass is not able to draw multiple layers simultanously.<br></blockquote></div><br>