[Top][All Lists]

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

Re[2]: [Gnash-commit] gnash ChangeLog server/parser/shape_character_d...

From: Udo Giacomozzi
Subject: Re[2]: [Gnash-commit] gnash ChangeLog server/parser/shape_character_d...
Date: Mon, 12 Nov 2007 22:06:50 +0100

Hello strk,

Monday, November 12, 2007, 9:09:26 PM, you wrote:
s> We'd need similar euristic for proper and performant withinSquareDistance
s> test for curves. The classic approach seems to be approximate and compute
s> distances, so knowing the actual rendering scale would help finding
s> an appropriate approximation. I guess this still needs a Gui handler
s> in the movie_root, or we'll miss the actual on-screen pixel scale...

You need to know the actual rendering scale anyway to know if the
stroke is magnified. Remember all strokes are at least one physical
pixel wide (hairline), even if they are downsized. Relative to the
definition this means the stroke width is increased.

Besides of that I don't know what you are talking about...?

Anyway, don't forget that the convert-everything-to-shapes approach
would eliminate the need to check the strokes (and would make handling
of dynamic shapes tricky...aaarghh).


reply via email to

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