mirror of
https://github.com/brl/mutter.git
synced 2024-12-23 11:32:04 +00:00
util: tune point_in_poly test for polys in screen coords
This makes a change to the original point_in_poly algorithm from: http://www.ecse.rpi.edu/Homepages/wrf/Research/Short_Notes/pnpoly.html The aim was to tune the test so that tests against screen aligned rectangles are more resilient to some in-precision in how we transformed that rectangle into screen coordinates. In particular gnome-shell was finding that for some stage sizes then row 0 of the stage would become a dead zone when going through the software picking fast-path and this was because the y position of screen aligned rectangles could end up as something like 0.00024 and the way the algorithm works it doesn't have any epsilon/fuz factor to consider that in-precision. We've avoided introducing an epsilon factor to the comparisons since we feel there's a risk of changing some semantics in ways that might not be desirable. One of those is that if you transform two polygons which share an edge and test a point close to that edge then this algorithm will currently give a positive result for only one polygon. Another concern is the way this algorithm resolves the corner case where the horizontal ray being cast to count edge crossings may cross directly through a vertex. The solution is based on the "idea of Simulation of Simplicity" and "pretends to shift the ray infinitesimally down so that it either clearly intersects, or clearly doesn't touch". I'm not familiar with the idea myself so I expect a misplaced epsilon is likely to break that aspect of the algorithm. The simple solution this patch applies is to pixel align the polygon vertices which should eradicate most noise due to in-precision. https://bugzilla.gnome.org/show_bug.cgi?id=641197
This commit is contained in:
parent
25db8d0653
commit
b3d9f313d4
@ -1699,7 +1699,7 @@ try_checking_point_hits_entry_after_clipping (CoglJournalEntry *entry,
|
||||
software_clip_entry (entry, vertices, &clip_bounds);
|
||||
entry_to_screen_polygon (entry, vertices, poly);
|
||||
|
||||
*hit = _cogl_util_point_in_poly (x, y, poly, sizeof (float) * 4, 4);
|
||||
*hit = _cogl_util_point_in_screen_poly (x, y, poly, sizeof (float) * 4, 4);
|
||||
return TRUE;
|
||||
}
|
||||
|
||||
@ -1753,7 +1753,7 @@ _cogl_journal_try_read_pixel (CoglJournal *journal,
|
||||
|
||||
entry_to_screen_polygon (entry, vertices, poly);
|
||||
|
||||
if (!_cogl_util_point_in_poly (x, y, poly, sizeof (float) * 4, 4))
|
||||
if (!_cogl_util_point_in_screen_poly (x, y, poly, sizeof (float) * 4, 4))
|
||||
continue;
|
||||
|
||||
/* FIXME: the journal should have a back pointer to the
|
||||
|
@ -28,7 +28,7 @@
|
||||
G_BEGIN_DECLS
|
||||
|
||||
int
|
||||
_cogl_util_point_in_poly (float point_x,
|
||||
_cogl_util_point_in_screen_poly (float point_x,
|
||||
float point_y,
|
||||
void *vertices,
|
||||
size_t stride,
|
||||
|
@ -38,10 +38,36 @@
|
||||
#include "config.h"
|
||||
#endif
|
||||
|
||||
#include "cogl-util.h"
|
||||
|
||||
#include <glib.h>
|
||||
|
||||
/* We've made a notable change to the original algorithm referenced
|
||||
* above to make sure we have reliable results for screen aligned
|
||||
* rectangles even though there may be some numerical in-precision in
|
||||
* how the vertices of the polygon were calculated.
|
||||
*
|
||||
* We've avoided introducing an epsilon factor to the comparisons
|
||||
* since we feel there's a risk of changing some semantics in ways that
|
||||
* might not be desirable. One of those is that if you transform two
|
||||
* polygons which share an edge and test a point close to that edge
|
||||
* then this algorithm will currently give a positive result for only
|
||||
* one polygon.
|
||||
*
|
||||
* Another concern is the way this algorithm resolves the corner case
|
||||
* where the horizontal ray being cast to count edge crossings may
|
||||
* cross directly through a vertex. The solution is based on the "idea
|
||||
* of Simulation of Simplicity" and "pretends to shift the ray
|
||||
* infinitesimally down so that it either clearly intersects, or
|
||||
* clearly doesn't touch". I'm not familiar with the idea myself so I
|
||||
* expect a misplaced epsilon is likely to break that aspect of the
|
||||
* algorithm.
|
||||
*
|
||||
* The simple solution we've gone for is to pixel align the polygon
|
||||
* vertices which should eradicate most noise due to in-precision.
|
||||
*/
|
||||
int
|
||||
_cogl_util_point_in_poly (float point_x,
|
||||
_cogl_util_point_in_screen_poly (float point_x,
|
||||
float point_y,
|
||||
void *vertices,
|
||||
size_t stride,
|
||||
@ -58,6 +84,11 @@ _cogl_util_point_in_poly (float point_x,
|
||||
float vert_yj = *(float *)((guint8 *)vertices + j * stride +
|
||||
sizeof (float));
|
||||
|
||||
vert_xi = COGL_UTIL_NEARBYINT (vert_xi);
|
||||
vert_xj = COGL_UTIL_NEARBYINT (vert_xj);
|
||||
vert_yi = COGL_UTIL_NEARBYINT (vert_yi);
|
||||
vert_yj = COGL_UTIL_NEARBYINT (vert_yj);
|
||||
|
||||
if (((vert_yi > point_y) != (vert_yj > point_y)) &&
|
||||
(point_x < (vert_xj - vert_xi) * (point_y - vert_yi) /
|
||||
(vert_yj - vert_yi) + vert_xi) )
|
||||
|
Loading…
Reference in New Issue
Block a user