The size of the monitor shouldn't have much (or anything in most cases) to do with this.
Important questions: Which version is being used? Which OS How is the display set? If it is set to constrain display resolution to match map, this could happen. However, the default behavior for a long time is to create display output at display resolution (depends on the size of the display window). Even with big monitors, this is not a huge file by GRASS GIS standards. However, the temp files that are created for the displays will be larger when larger windows are used on larger monitors (i.e., more pixels to render). Michael ______________________________ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-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 On Aug 13, 2012, at 12:00 PM, <[email protected]<mailto:[email protected]>> wrote: From: Markus Neteler <[email protected]<mailto:[email protected]>> Date: August 13, 2012 7:57:39 AM MST To: GRASS developers list <[email protected]<mailto:[email protected]>> Subject: Re: [GRASS-dev] Speed map display in wxGUI on bigger monitors On Fri, Aug 3, 2012 at 4:19 PM, Markus Neteler <[email protected]<mailto:[email protected]>> wrote: Hi, when working with the wxGUI on bigger monitors, it is rather slow when it comes to map display. Looking into the /tmp/ directory, I find fairly huge files which are generated and then combined for display. It is getting even worse when using GRASS over network. Question: why the uncompressed PNM/PPM format used by g.pnmcomp? ... I am still interested to understand this... thanks Markus
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
