Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project!

Re: [Vxl-maintainers] vgl_polygon_scan_iterator problem

 Re: [Vxl-maintainers] vgl_polygon_scan_iterator problem From: Peter Vanroose - 2004-04-30 16:26:47 ```> When y=786, it produced a very large value for xr That's not the only error: The point (785,424) should not be included, and neither should the points with y=791 (and certainly not the ones with x=411 to x=423). I'm having a look at it but I cannot promise that I'll find a solution :-) -- Peter. ```

 [Vxl-maintainers] vgl_polygon_scan_iterator problem From: Gehua Yang - 2004-04-29 03:23:35 Attachments: test.txt ```For these four vertices, vgl_polygon_scan_iterator failed to properly fill the polygon. 424 785.99975 426 786.00012 426 789.91188 424 790.06225 When y=786, it produced a very large value for xr(details in the attached text file). It worked on VXL version from 6/7/2003. Could someone take a look at it? Thanks. Gary ```
 Re: [Vxl-maintainers] vgl_polygon_scan_iterator problem From: Peter Vanroose - 2004-04-30 16:26:47 ```> When y=786, it produced a very large value for xr That's not the only error: The point (785,424) should not be included, and neither should the points with y=791 (and certainly not the ones with x=411 to x=423). I'm having a look at it but I cannot promise that I'll find a solution :-) -- Peter. ```
 Re: [Vxl-maintainers] vgl_polygon_scan_iterator problem From: Peter Vanroose - 2004-04-30 21:31:16 ```> For these four vertices, vgl_polygon_scan_iterator failed to properly fill > the polygon. > > 424 785.99975 > 426 786.00012 > 426 789.91188 > 424 790.06225 > > When y=786, it produced a very large value for xr. I have partially solved this problem (the large values disappeared) but it's still incorrect (the x values from 411 to 423 are still there). > It worked on VXL version from 6/7/2003. In the 6/7/03 version, essentially, the "no-boundary points" option was in effect, at least in the vertical direction. To more or less revert to the 6/7/03 behaviour, you may use the vgl_polygon_scan_iterator constructor with "false" as second argument. This solves the 411--423 problem as well. -- Peter. ```