<?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"
	>
<channel>
	<title>Comments on: Secrets of the Windows Mobile Home Screen API</title>
	<atom:link href="http://blog.enterprisemobile.com/index.php/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/</link>
	<description>Blogging about Windows Mobile, mobile devices, security, management and deployments.</description>
	<pubDate>Tue, 06 Jan 2009 01:16:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Pila</title>
		<link>http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-266</link>
		<dc:creator>Pila</dc:creator>
		<pubDate>Mon, 28 Jul 2008 11:54:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-266</guid>
		<description>I think it will help me as i have a Blackjack device.</description>
		<content:encoded><![CDATA[<p>I think it will help me as i have a Blackjack device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kdutta</title>
		<link>http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-233</link>
		<dc:creator>kdutta</dc:creator>
		<pubDate>Wed, 16 Jul 2008 04:25:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-233</guid>
		<description>I didn't have any issues with the WndProc causing crashes. I only took certain key events, and passed the rest of the events on using CallWindowProc. Make sure you reset the old window proc when the home screen changes (your plugin is released).

You can filter those OS messages too via the WndProc probably... similar to how you are setting the RSK.</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t have any issues with the WndProc causing crashes. I only took certain key events, and passed the rest of the events on using CallWindowProc. Make sure you reset the old window proc when the home screen changes (your plugin is released).</p>
<p>You can filter those OS messages too via the WndProc probably&#8230; similar to how you are setting the RSK.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Mujhe</title>
		<link>http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-232</link>
		<dc:creator>Joseph Mujhe</dc:creator>
		<pubDate>Wed, 16 Jul 2008 01:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-232</guid>
		<description>Hi All.

Hard work to do this! I'm trying to do something similar, but the entire code is in unmanaged code. But trying to subclass the home.exe WndProc is causing a lot of crashes! Has It happen with you?

Other big problem I'm facing is to change the RSK of the Desktop toolbar. I can change it via WM_Messages but when the device receives some O.S. commands (like new message) causes some inconsistency. 

Any ideas?

Thanks!

Joseph Mujhe</description>
		<content:encoded><![CDATA[<p>Hi All.</p>
<p>Hard work to do this! I&#8217;m trying to do something similar, but the entire code is in unmanaged code. But trying to subclass the home.exe WndProc is causing a lot of crashes! Has It happen with you?</p>
<p>Other big problem I&#8217;m facing is to change the RSK of the Desktop toolbar. I can change it via WM_Messages but when the device receives some O.S. commands (like new message) causes some inconsistency. </p>
<p>Any ideas?</p>
<p>Thanks!</p>
<p>Joseph Mujhe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kdutta</title>
		<link>http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-221</link>
		<dc:creator>kdutta</dc:creator>
		<pubDate>Thu, 10 Jul 2008 17:03:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-221</guid>
		<description>Getting into managed code on the Pocket PC Today Sceen is relatively easier from what I understand. You can create a regular System.Windows.Form/Control, and then parent it to your plugin window. Haven't messed around with it at all though.</description>
		<content:encoded><![CDATA[<p>Getting into managed code on the Pocket PC Today Sceen is relatively easier from what I understand. You can create a regular System.Windows.Form/Control, and then parent it to your plugin window. Haven&#8217;t messed around with it at all though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Hall</title>
		<link>http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-219</link>
		<dc:creator>Malcolm Hall</dc:creator>
		<pubDate>Thu, 10 Jul 2008 11:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprisemobile.com/2008/07/the-dirty-tricks-of-the-windows-mobile-home-screen-api/#comment-219</guid>
		<description>Very cool post, this is one of my favourite topics at the moment. Shared memory sounds interesting but when I built my C# homescreen plugin a few months ago I decided instead to create about 3 custom window message IDs to use to pass the dimensions and the HDC, then I wrapped up all of the real plugin messages in a custom ones and forwarded it to C#. I haven't published my code yet either because I am trying to make it cross platform between pocket pc and smartphone using some abstraction. That is getting messy though.

By the way I have recently spotted a third person who has solved this problem too, the project is called Throttle Launcher and uses a Pocket PC plugin. No source code either but you can have a peak with Reflector.</description>
		<content:encoded><![CDATA[<p>Very cool post, this is one of my favourite topics at the moment. Shared memory sounds interesting but when I built my C# homescreen plugin a few months ago I decided instead to create about 3 custom window message IDs to use to pass the dimensions and the HDC, then I wrapped up all of the real plugin messages in a custom ones and forwarded it to C#. I haven&#8217;t published my code yet either because I am trying to make it cross platform between pocket pc and smartphone using some abstraction. That is getting messy though.</p>
<p>By the way I have recently spotted a third person who has solved this problem too, the project is called Throttle Launcher and uses a Pocket PC plugin. No source code either but you can have a peak with Reflector.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
