I just recompiled GRASS 7.1 and posted it to my website (7.0 beta and 6.4 beta coming soon). Here is something I noticed when I last compiled GRASS 7.1 in May and which is still happening.
The first time I launch 7.1 and try to view a map (e.g., elevation from the NC demo data) it takes a REALLY long time…many minutes. Then it takes almost as long if I want to render it in 3D. When I switch back to 2D, a couple of the 3D buttons (rotate 3D scene and fly through mode) remain on the button bar. If I then quit GRASS and start it again, everything renders at normally fast speed and the button bar is OK. It seems to run fine from that point on. so it is is just the very first time that GRASS is launched. Others might want to check to see if this happens to them when they install the Mac (or other) 7.1 binaries and try to start them for the first time. I don’t know what is going on. Is Python trying to compile ALL of its source wxPython files while rendering a map for the first time? I don’t know. Something to look out for, especially with new users. Michael ______________________________ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Head, Graduate Faculty in Complex Adaptive Systems Science Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www: http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
