Helena and others,

I posted my proposed fix for volume display on the Mac (both isosurfaces and 
slices) to the trak report.

Unfortunately, Markus Metz's fix this morning did not work. So it is still 
getting rid of gvl_data_align that works so far.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice:  480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:          480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu




On Feb 3, 2013, at 2:00 AM, 
<[email protected]<mailto:[email protected]>>
 wrote:

From: Helena Mitasova <[email protected]<mailto:[email protected]>>
Subject: Re: [GRASS-dev] GRASS GIS 6.4.3RC2 released
Date: February 2, 2013 5:30:23 PM MST
To: Helmut Kudrnovsky <[email protected]<mailto:[email protected]>>
Cc: <[email protected]<mailto:[email protected]>>



On Feb 2, 2013, at 6:36 PM, Helmut Kudrnovsky wrote:

A second release candidate of GRASS GIS 6.4.3 is now available.

since it's more than a month ago now, what about another another RC or
release?

maybe anything for the community sprint next week?

Excellent suggestion. There is a number of unresolved issues, but hopefully not 
too difficult to fix:

- r3.in.ascii broken handling of input parameters (it runs only with defaults, 
if you need to change something,
e.g. specify * for nulls it gives error - more details here
http://trac.osgeo.org/grass/ticket/1801

- the isosurfaces now work on macosx10.8 with changes made by Michael - this 
needs to be further tested and
done for GRASS6.4.3 as well - Michael, can you put your solution into bug 
report #1736 and then
if it works perhaps this can be closed (btw I found #803 with isosurfaces 
crashing on linux with segfault -
I am wondering whether this was related).

_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to