Details Ticket 853


Comment | Reply | Take | Open


Serial Number 853
Subject v.digit: bug with area labeling (and another wish)
Area bug
Queue grass
Requestors neteler@itc.it
Owner none
Status resolved
Last User Contact Fri Mar 22 10:00:22 2002 (6 yr ago)
Current Priority 70
Final Priority 70
Due No date assigned
Last Action Wed Apr 3 10:18:44 2002 (6 yr ago)
Created Sat Nov 17 14:24:56 2001 (7 yr ago)

Transaction History Ticket 853


Sat, Nov 17 2001 14:24:56    Request created by neteler@itc.it  
Return-Path <neteler@itc.it>
Delivered-To grass-bugs@lists.intevation.de
Date Sat, 17 Nov 2001 14:24:47 +0100
From Markus Neteler <neteler@itc.it>
To grass5 developers list <grass5@grass.itc.it>
Cc grass-bugs@intevation.de
Subject v.digit fixed (and another wish and a bug)
Message-ID <20011117142447.A2069@itc.it>
Mail-Followup-To grass5 developers list <grass5@grass.itc.it>, grass-bugs@intevation.de
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
User-Agent Mutt/1.2.5i
Hi,

I think I have fixed the "NOTE: 1 new node needed" bug in v.digit.
The problem was that the number of points needed for snapped lines
was not reduced in

libes/vect32/diglib/check_node.c
(fixed). Radim, can you update for the grass51/ library?

Additionally I have
 - improved the related messages in v.digit (feel free to modify again)
 - changed to always get a threshold recommendation when entering a
   unacceptable snapping threshold (was restricted to digitizing boards)

Please test the fixes (compile the diglib first).

Now a wish: Is it possible to make the cursor center in v.digit transparent?
That would be a great help when digitizing polygons and setting the last =
first point.

Another bug not yet fixed is:
When digitizing areas, the internal line type seems to stay "line", not
area for the category labels. Also the label point is not correctly set
for areas when using the auto-label feature: the point is on the
area border, not within the area (will cause topological troubles).
This must be fixed in my opinion.

Cheers

 Markus


Tue, Jan 8 2002 14:51:01    Subject changed to v.digit: bug with area labeling ixed (and another wish and a bug) by mneteler  
Tue, Jan 8 2002 14:51:11    Subject changed to v.digit: bug with area labeling (and another wish) by mneteler  
Tue, Jan 8 2002 14:51:41    Area changed to bug by mneteler  
Fri, Mar 22 2002 10:00:22    Mail sent by mneteler  
> 853 sounds like release critical?
 
Yes, I think so. When digitizing areas in v.digit and using the
text label function, the area labeling is done as if the area
were a line. That causes problems later.
Needs to be verified by someone else.

Markus
Tue, Mar 26 2002 10:38:01    Priority changed to 70 by mneteler  
Tue, Mar 26 2002 14:36:19    Comments added by mneteler  
>
> this looks like an interesting improvement. Will this affect
> d.what.* and probably also v.digit (see bug/wish #853 in RT)?
 
It affects anything which reads mouse clicks from the monitor.
 
AFAICT, this corresponds to the wish part of #853. The new cursor is
almost identical to the old one (standard XC_crosshair cursor), except
that the central pixel (the cursor's hotspot) is transparent.
 
--
Glynn Clements <glynn.clements@virgin.net>
Wed, Apr 3 2002 10:18:40    Comments added by mneteler  
The area label bug is no bug. AutoLabel function labels only "area edges",
not areas. Have changed the user message to be clear.

Markus
Wed, Apr 3 2002 10:18:44    Status changed to resolved by mneteler  
Comment | Reply | Take | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request