<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Common mistakes when using hitTestPoint function of a DisplayObject</title>
	<atom:link href="http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Sat, 02 Jun 2012 13:09:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MikeG</title>
		<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/comment-page-1/#comment-25660</link>
		<dc:creator>MikeG</dc:creator>
		<pubDate>Mon, 09 Jan 2012 09:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.open-design.be/?p=474#comment-25660</guid>
		<description>Thanks, it helped me:)</description>
		<content:encoded><![CDATA[<p>Thanks, it helped me:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iguess</title>
		<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/comment-page-1/#comment-22499</link>
		<dc:creator>iguess</dc:creator>
		<pubDate>Fri, 07 Oct 2011 20:28:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.open-design.be/?p=474#comment-22499</guid>
		<description>thank you, valuable information^</description>
		<content:encoded><![CDATA[<p>thank you, valuable information^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/comment-page-1/#comment-20892</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 17 Aug 2011 20:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.open-design.be/?p=474#comment-20892</guid>
		<description>Thanks, my problem was #3.</description>
		<content:encoded><![CDATA[<p>Thanks, my problem was #3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tarun</title>
		<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/comment-page-1/#comment-17973</link>
		<dc:creator>tarun</dc:creator>
		<pubDate>Sat, 16 Apr 2011 14:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.open-design.be/?p=474#comment-17973</guid>
		<description>thanks!!
#2 is very useful to me.
Please send me some examples of #3 as its hard to understand.</description>
		<content:encoded><![CDATA[<p>thanks!!<br />
#2 is very useful to me.<br />
Please send me some examples of #3 as its hard to understand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel</title>
		<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/comment-page-1/#comment-12893</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Mon, 01 Nov 2010 16:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.open-design.be/?p=474#comment-12893</guid>
		<description>From the Adobe documentation

DisplayObject.hitPointTest()

"Evaluates the display object to see if it overlaps or intersects with the point specified by the x and y parameters. The x and y parameters specify a point in the coordinate space of the Stage, not the display object container that contains the display object (unless that display object container is the Stage). "

Although a common mistake, it is there in the documentation in plain print.</description>
		<content:encoded><![CDATA[<p>From the Adobe documentation</p>
<p>DisplayObject.hitPointTest()</p>
<p>&#8220;Evaluates the display object to see if it overlaps or intersects with the point specified by the x and y parameters. The x and y parameters specify a point in the coordinate space of the Stage, not the display object container that contains the display object (unless that display object container is the Stage). &#8221;</p>
<p>Although a common mistake, it is there in the documentation in plain print.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kawika</title>
		<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/comment-page-1/#comment-9771</link>
		<dc:creator>Kawika</dc:creator>
		<pubDate>Thu, 02 Sep 2010 22:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.open-design.be/?p=474#comment-9771</guid>
		<description>Thanks so much!  #3 was exactly what I was looking for!  How come no one TELLS you these things in the Flash documentation?  I was ready to tear my hair out on a client project!</description>
		<content:encoded><![CDATA[<p>Thanks so much!  #3 was exactly what I was looking for!  How come no one TELLS you these things in the Flash documentation?  I was ready to tear my hair out on a client project!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blog.open-design.be/2009/04/25/common-mistakes-when-using-hittestpoint-function-of-a-displayobject/comment-page-1/#comment-8147</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 13 Jun 2010 16:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.open-design.be/?p=474#comment-8147</guid>
		<description>I have been looking for an answer to a bug I have in my game and number 3 was exactly what I needed to find. My hero would fall through the level because I started using a camera. The localToGlobal should fix that though, I think. Many thanks!</description>
		<content:encoded><![CDATA[<p>I have been looking for an answer to a bug I have in my game and number 3 was exactly what I needed to find. My hero would fall through the level because I started using a camera. The localToGlobal should fix that though, I think. Many thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

