#955: v.digit background errors ----------------------+----------------------------------------------------- Reporter: clerici | Owner: [email protected] Type: defect | Status: closed Priority: normal | Milestone: 6.4.0 Component: Vector | Version: 6.4.0 RCs Resolution: wontfix | Keywords: vector, digitizing Platform: All | Cpu: All ----------------------+----------------------------------------------------- Changes (by mmetz):
* status: new => closed * component: default => Vector * platform: Linux => All * keywords: => vector, digitizing * resolution: => wontfix * cpu: Unspecified => All Comment: Replying to [ticket:955 clerici]: > The d.vect command in the Background panel of v.digit gives an error regarding topology rebuilding[[BR]] Using the very same vector map that is edited as background does not work because it gets modified and topology info is only updated when v.digit is closed. The only way that would work is to update and write out topology every time something is changed. This is not an option because then v.digit would be incredibly slow. It also doesn't really make sense because the vector map to be digitized is displayed anyway. Therefore... > 4) In the background panel the command 'd.vect map=roads_c...@esercizi color=0:0:0 ..........' is displayed by default.[[BR]] ...is this a bug in the tcltk GUI. > Entering v.digit through: Vector>Develop map>Digitize the Background panel is empty.[[BR]] > I added the command 'd.vect map=roads_copy disp=cat' and I moved a node. In redrawing, the cat values were not displayed and I had the same error as in Fig.1.[[BR]] ..and this will not work, i.e. produce the error you observed. > > > I entered at the GRASS prompt the command: v.digit map=roads_copy map=roads_copy bgcmd='d.vect map=roads_copy disp=cat'. Moving a node and redrawing, the cat values were correctly displayed and two WARNING were reported in the terminal (Fig.2). ..same as above. If you want to compare changes, the only option is to first create a copy of the vector map and use that as background. As above, this won't fix because v.digit would become even slower than it is already. If possible, use the new wxGUI digitizer (more features, faster, less memory). -- Ticket URL: <http://trac.osgeo.org/grass/ticket/955#comment:1> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
