<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx</link><description>Hi all, welcome back, 
 I've been working on an issue where WM_SIZE events are not properly generated once the nesting hierarchy of windows exceeds a certain depth. This issue only occurs on current x64 Windows : like XP, Server 2008 or the latest Windows</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10331006</link><pubDate>Wed, 18 Jul 2012 06:58:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10331006</guid><dc:creator>Alejandro Campos Magencio</dc:creator><description>&lt;p&gt;Hi Thiago,&lt;/p&gt;
&lt;p&gt;If I recall well, there could be things like hooks that could reduce the number of nested levels before the issue happens.The limitation should be the same in all Win7 x64, unless they recently changed something (hotfix) that it is installed in some of your machines but not in others...&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10331006" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10330857</link><pubDate>Tue, 17 Jul 2012 21:45:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10330857</guid><dc:creator>Thiago Almeida</dc:creator><description>&lt;p&gt;Hi, Alejandro. Thanks for shedding some light on this topic.&lt;/p&gt;
&lt;p&gt;Do you have any information on why this limitation is hit on some installations of Win7 x64, but not all of them?&lt;/p&gt;
&lt;p&gt;On some machines, this limitation is being hit quite easily. Is there any way to isolate the machines (hardware + Win7 installation) that are most affected?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10330857" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10297939</link><pubDate>Thu, 26 Apr 2012 08:31:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10297939</guid><dc:creator>Alejandro Campos Magencio</dc:creator><description>&lt;p&gt;Hi Camilio, &lt;/p&gt;
&lt;p&gt;Yes, I know about the KB article, as I requested it to our Documentation team and participated in the writting :-)&lt;/p&gt;
&lt;p&gt;Cheers!&lt;/p&gt;
&lt;p&gt;Alex&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10297939" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10297937</link><pubDate>Thu, 26 Apr 2012 08:25:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10297937</guid><dc:creator>Camilio</dc:creator><description>&lt;p&gt;FYI, there is a kb on this problem. but this does not helps more than this article! Thanks&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/kb/2664641/en-us"&gt;support.microsoft.com/.../en-us&lt;/a&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10297937" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10268312</link><pubDate>Wed, 15 Feb 2012 17:15:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10268312</guid><dc:creator>Josh Farquharson</dc:creator><description>&lt;p&gt;I had to make 2 suddle changes to get this to work correctly. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;1. When overriding OnSizeChanged, I had to prevent the base.OnSizeChanged from being called. &amp;nbsp;If it it continued to call into the base class, I still saw the redraw issue.&lt;/p&gt;
&lt;p&gt;2. In the ChangeSize method, instead of checking if the handle is null, you&amp;#39;ll need to check &amp;quot;IsHandleCreated&amp;quot;. &amp;nbsp;The Handle property getter actually creates a handle and causes the controls Load event to fire which could cause some issues if you&amp;#39;re doing some setup logic in the OnLoad event.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10268312" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10168372</link><pubDate>Wed, 25 May 2011 18:41:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10168372</guid><dc:creator>Ryan Rastedt</dc:creator><description>&lt;p&gt;FYI, there is a KB article out there, dated June 2008:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/kb/953934"&gt;support.microsoft.com/.../953934&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Also, checking for a handle via (this.Handle != null) is bad news as accessing the Handle property will force the handle to be created. &amp;nbsp;I had run into an issue where the handle was recreating itself after disposal started, not a fun one to track down. &amp;nbsp;I recommend using the IsHandleCreated property instead.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10168372" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10166079</link><pubDate>Wed, 18 May 2011 22:18:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10166079</guid><dc:creator>Steve Squires</dc:creator><description>&lt;p&gt;Jeremy Streeter&amp;#39;s solution (code repeated below) was added to base controls on my project. This &amp;nbsp;resolved the issue for me in a pretty unintrusive way. Thanks Jeremy!&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;protected override void OnSizeChanged(EventArgs e)&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;{&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;if (this.Handle != null)&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;{&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;this.BeginInvoke((MethodInvoker)delegate&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;{&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;base.OnSizeChanged(e);&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;});&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;}&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;}&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10166079" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10164362</link><pubDate>Fri, 13 May 2011 20:36:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10164362</guid><dc:creator>Juan Monachesi</dc:creator><description>&lt;p&gt;Also any QA team checking this problem should open the tested software with Spy++ running, as it reproduces all the different scenarios like having a specials drivers such as in the Logitech and Wacom issues.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10164362" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10163572</link><pubDate>Wed, 11 May 2011 22:32:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10163572</guid><dc:creator>Juan Monachesi</dc:creator><description>&lt;p&gt;In ATL we had to use several methods: &lt;/p&gt;
&lt;p&gt;We subclassed our main control container (the CAxWindow&amp;#39;s HWND) to delay the WM_SIZE with PostMessage. But that wasn&amp;#39;t enough so we also had to use a thread to call some of the SetWindowPos in another thread.&lt;/p&gt;
&lt;p&gt;You may wanna check if the process is working in x64 before doing this, because all these nasty workarounds make the resize a lot laggier so at least in x86 the resize doesn&amp;#39;t suffer.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10163572" width="1" height="1"&gt;</description></item><item><title>re: Controls won't get resized once the nesting hierarchy of windows exceeds a certain depth (x64)</title><link>http://blogs.msdn.com/b/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx#10150470</link><pubDate>Wed, 06 Apr 2011 14:04:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10150470</guid><dc:creator>Alejandro Campos Magencio</dc:creator><description>&lt;p&gt;There is no MSDN page or KB about this as far as I know... The solutions I know are in the post, and other solutions can be found within the comments of the post...&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10150470" width="1" height="1"&gt;</description></item></channel></rss>