Greetings from Idaho !

Just when I start bragging about this bulletin board to others ...

I sent in a message on August 7 regarding the .dig_cfg file and how to
decipher it.  I also sent a message to the SCS bulletin board and then
figured I would get a message back from here sooner.  Actually, I have
not received word from either!

I'll repeat the question and hope someone just missed my earlier help
message and responds here.

>One of our GRASS systems had problems yesterday in v.digit and I would
>appreciate any help fellow GRASS mystery solvers could lend.
>
>The operator was unable to break a line because the point device was set
>to the digitizer and the operator chose NONE for a digitizer at the start-up
>of the digitizing session, just to do some on-screen corrections.   However,
>since the operator did choose NONE, v.digit does not allow changing of the
>window, point, and digitizing functions in the Customize screens (the w, p,
>and z functions).  I don't know how the point function got stuck on the
>digitizer, or why GRASS allows that to happen when NONE is selected at the
>start-up, but it has happened before and will probably continue (this is
>still 4.0 though, maybe better things in 4.1).
>
>A colleague in Montana suggested editing the .dig_cfg file in the 
>$LOCATION/.tmp directory, but she wasn't sure what characters to edit.  The
>way I have had to solve this in times past was to exit v.digit, start it
>up again but pick a digitizer, register the map, go in and change the
>Customize options all to MOUSE, exit saving the changes, then go back in
>to v.digit, choosing NONE, and all is back to normal.
>
>This time I chose to edit the .dig_cfg file that looked like this on the
>system:
>
>9.144000 18.288000
>0 0 1 0 1 1 0 1 1 0 0 1 0
>4 8 6 10 9 7 7 7 9 3 2 7 7 6 6 5
>1 0 1 0 0 1 0
>
>I figured all the 0's and 1's meant that Customized Options were turned ON
>or OFF and that the numbers in the third row stood for Color Options.  I
>changed all the 0's to 1's in the fourth row, and when the operator went
>back in to v.digit, all Options were turned back to the mouse and the
>operator thought I was some sort of GRASS genius!  The only problem was
>that I had no idea what I was changing; I just happened to get lucky on the
>first try!  I don't really have the time to test each one of the characters
>to find out what it does, so ...
>
>Boiling this down to a few questions instead of a true-life story on
>sleuthing GRASS mysteries:
>
>        1.  What corresponding v.digit Options does each of the
>            characters in the .dig_cfg file stand for?
>
>        2.  What can be done to prevent this business of a digitizer
>            being picked for the Point device when no digitizer is
>            specified in the v.digit start-up?
>
>My thanks in advance.  Respond to grassu-list, FAX the solution, or give 
>me a call.

David Hoover
Idaho State GIS Specialist
USDA - Soil Conservation Service
Boise, Idaho
208-334-1525  (208-334-9230 FAX)