[GRASS-dev] [GRASS GIS] #1270: wingrass: Error in Attribute Table Manager

[GRASS GIS]

#1270: wingrass: Error in Attribute Table Manager
-----------------------------------------------+----------------------------
 Reporter:  antonioall                         |       Owner:  grass-dev@…              
     Type:  defect                             |      Status:  new                      
 Priority:  blocker                            |   Milestone:  6.4.3                    
Component:  wxGUI                              |     Version:  svn-develbranch6         
 Keywords:  wingrass, attribute table manager  |    Platform:  MSWindows Vista          
      Cpu:  x86-32                             |  
-----------------------------------------------+----------------------------

Comment(by hamish):

 Replying to [comment:12 neteler]:
 > I guess that http://trac.osgeo.org/grass/changeset/55106 will now
 > block any testing.

 not really, just use devbr6 for testing, or open up dbmgr/manager.py in
 notepad++ or TextPad or whatever favourite text editor under Windows and
 comment-out the comment-out. The idea of r55106 is to have relbr64 ready
 for release now, and to continue the debugging in the dev branches. aka
 this doesn't look like it is being resolved in a hurry, and if we leave it
 blocking 6.4.3 then the release may take a long time.

 is there a wxPy way to grey-out entire tabs? the manage tables and manage
 layers tabs don't give much feedback that they're disabled beyond "(read-
 only)" in the window title super-tab. the connection info may still be
 interesting to see, so fully blocking access to reading what's there
 wouldn't be the ideal way to do that.. ?


 with the r55185-512 6.4.3svn nightly build on Windows7 64bit running the
 desktop icon wxGUI, I still get an error. Actually it froze with an
 endless spinning circle hourglass thing when I tried to add a column in
 the "show attribute data" manage tables tab, with the cursor over any of
 the open grass windows. I had to kill it by clicking on the "X" in the
 window, which took out all of grass except a zombie dbf.exe in the task
 manager + the empty cmd.exe dosbox.

 moreover, using v.db.addcol from the main db -> vect db conns menu to add
 a column had this error:
 {{{
 v.db.addcol --verbose map=copyofbugs2 at user1 columns=someint2 integer
 DBMI-DBF driver error:
 ERROR: Unable to open database <C:/Program Files (x86)/GRASS GIS
 6.4.3svn/msys/Users/Hamish/Documents/GIS DataBase/spearfish60/user1/dbf/>
 ERROR: Cannot continue (problem adding column).
 }}}

 Somehow ProgramFiles....msys (GISBASE) is sneaking into the GISDBASE.  ??

 and again there's a dbf.exe zombie in the task manager, so when you try to
 quit the empty dos box lurking in the background won't exit without a `^C`
 in it or to kill the dbf.exe in the task manager. No lockup this way
 though.


 running v.db.connect from the same menu has everything looking as it
 should be:
 {{{
 v.db.connect -p map=copyofbugs2 at user1
 layer <1> table <copyofbugs2> in database </Users/Hamish/Documents/GIS
 DataBase\spearfish60\user1\dbf\> through driver <dbf> with key <cat>
 Vector map <copyofbugs2 at user1> is connected by:
 }}}

 well, everything except the order of stderr and stdout, but I can forgive
 that.


 On a hunch I tried dragging a file into the dbf/ folder directly, but it
 complied and didn't request that I do that as admin.


 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1270#comment:16>
GRASS GIS <http://grass.osgeo.org>