Change History (4)
comment:1 by , 16 years ago
Milestone: | → 1.5.1 |
---|
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 15 years ago
comment:4 by , 13 years ago
I just found a grave bug introduced by the previous fix. Under some circumstances (when the point array exactly corresponds to raster grid nodes and we are going through the array starting from that exactly corresponding point) the algorithm goes one step more than needed and returns the value in array which follows the correct one.
That should be fixed in trunk with r21129 and in 1.7 with r21131.
A number of appropriate tests were added with r21130.
Note:
See TracTickets
for help on using tickets.
This problem has been fixed.