I hate to say it, but I need to go back to GRASS 6.3. GRASS 6.4-svn keeps on freezing or unexpectedly quitting when I do anything more intense than view what I've already created. Will it be as simple as dumping Active Tcl (the Wish components) and reinstalling GRASS 6.3?
Also, the surface raster I generated from the ASCII files only displays white now. Is there anyway to recover that once I go back to 6.3?
I hate to say it, but I need to go back to GRASS 6.3. GRASS 6.4-svn keeps on freezing or unexpectedly quitting when I do anything more intense than view what I've already created.
Can you reproduce it and describe it using the spearfish sample data? I can check if it's a build problem.
Will it be as simple as dumping Active Tcl (the Wish components) and reinstalling GRASS 6.3?
If you are using my GRASS 6.3, there is no need to delete ActiveTcl. It has its own internal TclTk X11 binaries that it explicitly uses. In fact, no need to delete 6.3 before installing 6.4.
Also, the surface raster I generated from the ASCII files only displays white now. Is there anyway to recover that once I go back to 6.3?
First Pogril: Why is life like sticking your head in a bucket filled with hyena offal?
Second Pogril: I don't know. Why IS life like sticking your head in a bucket filled with hyena offal?
First Pogril: I don't know either. Wretched, isn't it?
On Nov 25, 2008, at 8:22 PM, William Kyngesburye wrote:
On Nov 25, 2008, at 6:53 PM, Kurt Springs wrote:
I hate to say it, but I need to go back to GRASS 6.3. GRASS 6.4-svn keeps on freezing or unexpectedly quitting when I do anything more intense than view what I've already created.
Can you reproduce it and describe it using the spearfish sample data? I can check if it's a build problem.
I tried but it seemed all right with spearfish. Is there something specific I could test. I tried working with the digitizer but I ran into a problem I mentioned earlier. Active Tcl doesn't seem to have a way to set the mouse button emulations. I tried the control, command and option/alt keys to no avail. I have a Logitech mouse, and I have left right and middle buttons set, but that didn't seem to help. Could you shed some light on what to do?
Will it be as simple as dumping Active Tcl (the Wish components) and reinstalling GRASS 6.3?
If you are using my GRASS 6.3, there is no need to delete ActiveTcl. It has its own internal TclTk X11 binaries that it explicitly uses. In fact, no need to delete 6.3 before installing 6.4.
6.4 actually overwrote 6.3. I'd assumed the reverse would be true.
Also, the surface raster I generated from the ASCII files only displays white now. Is there anyway to recover that once I go back to 6.3?
Rasters should be compatible between 6.4 and 6.3.
Something when v.digit crashed actually made it unreadable.
First Pogril: Why is life like sticking your head in a bucket filled with hyena offal?
Second Pogril: I don't know. Why IS life like sticking your head in a bucket filled with hyena offal?
First Pogril: I don't know either. Wretched, isn't it?
If you are using my GRASS 6.3, there is no need to delete ActiveTcl. It has its own internal TclTk X11 binaries that it explicitly uses. In fact, no need to delete 6.3 before installing 6.4.
6.4 actually overwrote 6.3. I'd assumed the reverse would be true.
Odd, GRASS 6.3 and 6.4 have different names:
GRASS-6.3.app
GRASS-6.4.app
Also, the surface raster I generated from the ASCII files only displays white now. Is there anyway to recover that once I go back to 6.3?
Rasters should be compatible between 6.4 and 6.3.
Something when v.digit crashed actually made it unreadable.
Also odd - why a vector would affect a raster. Or did you mean surface _vector_?
"This is a question about the past, is it? ... How can I tell that the past isn't a fiction designed to account for the discrepancy between my immediate physical sensations and my state of mind?"
It was a s a surface raster map generated from an ascii file. It just seems that when v.digit crashes, regardless of the version, I am in for trouble.
Kurt
On Nov 25, 2008, at 11:51 PM, William Kyngesburye wrote:
On Nov 25, 2008, at 10:33 PM, Kurt Springs wrote:
If you are using my GRASS 6.3, there is no need to delete ActiveTcl. It has its own internal TclTk X11 binaries that it explicitly uses. In fact, no need to delete 6.3 before installing 6.4.
6.4 actually overwrote 6.3. I'd assumed the reverse would be true.
Odd, GRASS 6.3 and 6.4 have different names:
GRASS-6.3.app
GRASS-6.4.app
Also, the surface raster I generated from the ASCII files only displays white now. Is there anyway to recover that once I go back to 6.3?
Rasters should be compatible between 6.4 and 6.3.
Something when v.digit crashed actually made it unreadable.
Also odd - why a vector would affect a raster. Or did you mean surface _vector_?
"This is a question about the past, is it? ... How can I tell that the past isn't a fiction designed to account for the discrepancy between my immediate physical sensations and my state of mind?"
On Nov 25, 2008, at 8:51 PM, William Kyngesburye wrote:
On Nov 25, 2008, at 10:33 PM, Kurt Springs wrote:
If you are using my GRASS 6.3, there is no need to delete ActiveTcl. It has its own internal TclTk X11 binaries that it explicitly uses. In fact, no need to delete 6.3 before installing 6.4.
6.4 actually overwrote 6.3. I'd assumed the reverse would be true.
Odd, GRASS 6.3 and 6.4 have different names:
GRASS-6.3.app
GRASS-6.4.app
I can confirm that the 6.4 install doesn't actually delete GRASS-6.3.app, it just "empties" it out. So that it is now 6.5 meg, while it used to be much larger (6.4 is 74 meg). And when I double click on 6.3 I get a error in my log:
posix_spawnp("/Applications/GRASS-6.3.app/Contents/MacOS/GRASS", ...): No such file or directory
So it looks like the 6.4 installer deletes most, but not all, of the stuff that was in 6.3.
On Dec 1, 2008, at 11:51 AM, Adam Dershowitz wrote:
On Nov 25, 2008, at 8:51 PM, William Kyngesburye wrote:
On Nov 25, 2008, at 10:33 PM, Kurt Springs wrote:
If you are using my GRASS 6.3, there is no need to delete ActiveTcl. It has its own internal TclTk X11 binaries that it explicitly uses. In fact, no need to delete 6.3 before installing 6.4.
6.4 actually overwrote 6.3. I'd assumed the reverse would be true.
Odd, GRASS 6.3 and 6.4 have different names:
GRASS-6.3.app
GRASS-6.4.app
I can confirm that the 6.4 install doesn't actually delete GRASS-6.3.app, it just "empties" it out. So that it is now 6.5 meg, while it used to be much larger (6.4 is 74 meg). And when I double click on 6.3 I get a error in my log:
posix_spawnp("/Applications/GRASS-6.3.app/Contents/MacOS/GRASS", ...): No such file or directory
So it looks like the 6.4 installer deletes most, but not all, of the stuff that was in 6.3._______________________________________________
I just tested it and just re-installing 6.3, while 6.4 is there, seems to allow both to coexist fine.
On Dec 1, 2008, at 1:57 PM, Adam Dershowitz wrote:
Odd, GRASS 6.3 and 6.4 have different names:
GRASS-6.3.app
GRASS-6.4.app
I can confirm that the 6.4 install doesn't actually delete GRASS-6.3.app, it just "empties" it out. So that it is now 6.5 meg, while it used to be much larger (6.4 is 74 meg). And when I double click on 6.3 I get a error in my log:
posix_spawnp("/Applications/GRASS-6.3.app/Contents/MacOS/GRASS", ...): No such file or directory
So it looks like the 6.4 installer deletes most, but not all, of the stuff that was in 6.3._______________________________________________
I just tested it and just re-installing 6.3, while 6.4 is there, seems to allow both to coexist fine.
Ah, this must be OSX installer magic. I've run into it with frameworks, but this is the first application "upgrade" that I've had to deal with.
When the installer "upgrades" an installation, it removes the older version as best it can. It uses the application ID to say whether an application is the same, in this case "org.osgeo.grass6".
I have configured the installers to allow "downgrading", so that is probably why installing 6.3 over 6.4 leaves 6.4 alone. (I wasn't quite sure what this really meant.)
I can look into options to disable the upgrade magic, or I may have to do what I do for framework upgrades, and temporarily move the old version before installing the new version (bleh). Or change the ID on each version.