> > The current code has the polygon's coordinates in the object's
> > coordinate space.
>
> That doesn't seem to be true. evas_object_polygon_point_add(obj,x,y)
> adds the point (x,y) to the list of points, not the point
> (x - min_x, y - min_y).
Like Brian, I too had thought that the interpretation was
the poly points were taken to be rel to whatever the obj's current
position.. but that's not so. The obj's pos is taken as the min of
the poly vertex coords, and thus you are correct that the present
poly positioning semantics is mostly borked.
Note that things like poly and line objs have never really
been given much attention in evas - they are still waiting for a
much more thorough rewrite at some point - and thus things there
are likely to be rather shabby right now (anyone who feels like
they would like to help setup a good, fast, path-rasterizer is more
than welcome to lend a hand :)).
Now, this actually brings up a question: Just what should
the interpretation be of vertex coords (in lines, polys,..), and
of the 'geometry' of such path-defined objs?
One could take the semantics to be that the vertices are
defined rel to whatever the obj's pos is, and have the obj's set
geometry clip the poly's extent. This seems more desirable to me...
jose.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
