[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[2]: [Gnash-dev] Re: point test

From: Udo Giacomozzi
Subject: Re[2]: [Gnash-dev] Re: point test
Date: Mon, 5 Nov 2007 01:29:47 +0100

Hello Sandro,

Sunday, November 4, 2007, 11:39:41 PM, you wrote:
>> Question: Does Flash' hit test method work with thick outlines too (or
>> just fills)?

SS> Think outlines too. I added this support in gnash exposing a
SS> withinSquareDistance interface to gnash::path.

Bad. So we would need to take care of the cap and join styles too. So,
one point for the renderer-based solution.

>> Is hit testing currently really a bottleneck?
SS> Nope, but it's not correct,

I was referring to the speed argument (and the caching).

SS> and if we need to normalize the paths
SS> to make it correct then it will be worth normalizing the paths once
SS> instead of at every hit test.

Ok, but what is effectively "normalizing"?

>> BTW, how would the caching mechanism work?

SS> I think the idea is that rather then calling normalize_path (which already
SS> exists and is used by different renderers) at display time we'd call it
SS> at first ::display and not again on next.

Can't find normalize_path. Do you mean point_normalize()?

>> Agree with the interface, but matrix information should be passed just
>> like with draw_shape() because the AGG backend uses the internal
>> matrix transformation methods of the AGG lib.

SS> The query point should be passed in "local" coordinates already,
SS> which is the same coordinate space as the edges.

The query point is not the problem. The shape itself must be
transformed (rotation etc.) :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]