Jesse,
I noticed another bug while playing around with snapping today: I could snap to
one end of a line, but not the other. I traced it down to the getClosest()
function in EditUtils:
for( int i = 1; i < coordinates.length; i++ ) { [EditUtils, Line 176]
should be
for( int i = 0; i < coordinates.length; i++ ) {
otherwise only one endpoint of a line will be searched.
Regards,
Michael
Jesse Eichar wrote:
>I've applied the patch and like the outcome. Thanks for it. I
>figured out the problem with the performance as well. It wasn't an
>SWT problem it was just a dumb mistake in the code that places the
>snap area circle.
>
>Thanks for the help,
>
>Jesse
>
>
>On 15-May-06, at 8:52 AM, Jesse Eichar wrote:
>
>>>
>>> The new snapping functionality added over the weekend looks great!
>>> It will definitely simplify feature entry for us...
>>>
>>> Two issues I noticed:
>>> 1. The new snapping functions seem to snap to pixels, and not
>>> coordinates. The problem occurs when the features being added are
>>> added at different zoom levels (i.e. draw a line, zoom in a bit,
>>> and draw another line that snaps to the first line. The snap will
>>> not be exact). I have attached a patch that should fix this, but
>>> I'm not sure how it will affect other operations.
>> Sweet! I'm going to play with this a bit for sure. Thanks a lot.
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
