I don't know if it only happens to you. We need to find someone with a lot of vector files to test it on now.
Have you tried GRASS 6.5 to see if it hangs there too? What platform are you on?
The fact that it works with TclTk is irrelevant. Completely different language and interface programming.
Do you get any slowness when you try to pick a vector map with all of your vectors present?
Michael
On Feb 24, 2010, at 6:57 AM, grass-user-request@lists.osgeo.org wrote:
Date: Tue, 23 Feb 2010 20:06:46 -0800 (PST)
From: georgew <gws293@hotmail.com>
Subject: [GRASS-user] Re: Bug or my fault?
To: grass-user@lists.osgeo.org
Message-ID: <1266984406223-4623610.post@n2.nabble.com>
Content-Type: text/plain; charset=us-ascii
Thanks for your help Michael. Here is the status.
Issued v.db.connect and all prints as expected by you and all vectors have a
corresponding .dbf file.
This is what I do.
I have a mapset with 270 vectors. I open GRASS64 with wxpython GUI and
select one vector in the middle, call it vect135. I right click to list the
attributes. The system hangs with error "Python.exe not responding"
I restart GRASS64 with TclTk GUI and load the same vector, press the
attributes button and all attributes show up perfectly.
I then delete the top 100 .dbf files from the dbf directory only (not from
the vector directory). I restart GRASS64 with the python GUI again, load the
same vector (vect135), right click and the attribute table shows up
perfectly.
I then restore the 100 .dbf files I had previously deleted and now delete
the bottom 100. Restart GRASS64 with python GUI, load vect135, right click
and the attribute table shows up perfectly.
As soon as the number of dbf files increases to approx 188 (the actual
number seems to depend on which vectors are involved) the system hangs when
opening the attribute table, but only with the python GUI.
I have now restructured my location so I have a number of mapsets and have
distributed the vectors among the new mapsets, so they all have less than
100 files each, and all works perfectly. But I am really puzzled and would
dearly like to know why this happens only to me!
By the way, the problem occurs running GRASS with or without MSys.
I don't know if it only happens to
you. We need to find someone with a lot of vector files to
test it on now.
I made a shell loop to create 300 v.random maps in a mapset with column= so
they all had dbfs. no problem opening and editing attr tables in the
wxGUI.
something like
for i in `seq 300` ; do
v.random out=test_$i n=20 zmax=1 column=rand_01 --quiet
done
Thanks for checking. I wonder if this is version, platform, or individual specific?
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
I don't know if it only happens to
you. We need to find someone with a lot of vector files to
test it on now.
I made a shell loop to create 300 v.random maps in a mapset with column= so
they all had dbfs. no problem opening and editing attr tables in the
wxGUI.
something like
for i in `seq 300` ; do
v.random out=test_$i n=20 zmax=1 column=rand_01 --quiet
done
Some more info.
My main platform is Win7 Pro, GRASS 6.4.0 standalone, Python 2.6.4.
But I have tried other platforms with identical setup, with the following
results:
1. All works well under Ubuntu 9.10.
2. But problem exists also in WinXP so it is not Win 7 specific, but it is
Windows specific.
You don't need a lot of vector files. You can have a single vector, then go
to the dbf directory and copy the single .dbf file in that same directory
(Windows will automatically give it a new name). Then copy all again in the
same directory and so on, after only 8 iterations you will have 256 files.
Open the original vector file in Grass and try to list the attribute table.
Unless there is something very specifically wrong with my setup, you should
experience the same problem I have.
And yes it is slow, very slow in fact, compared to Ubuntu which is almost
instantaneous in its response, and Win 7 is even slower than XP running as a
virtual machine!
I don't have grass 6.5 installed, so I cannot try it. If ther are Win
binaries available for it I will give it a go, but I need some more time.
Thanks again for your help
Thanks Marcus, I think our messages crossed, here is the result (see my
previou message):
I have just installed 6.5.svn-r41167-1 from the daily Win releases, into my
Win 7. It crashes at start-up with:
C:\programs\GRASS-65>grass65svn.bat
Traceback (most recent call last):
File "C:/programs/GRASS-65/etc/wxpython/gis_set.py", line 37, in
<module>
from gui_modules import help
File
"c:/osgeo4w/usr/src/grass6_devel/dist.i686-pc-mingw32/etc/wxpython/gui_mo
dules/help.py", line 25, in <module>
ImportError: No module named agw.customtreectrl
Traceback (most recent call last):
File "C:/programs/GRASS-65/etc/wxpython/wxgui.py", line 63, in <m
odule>
import wx.lib.agw.customtreectrl as CT
ImportError: No module named agw.customtreectrl