http://blogs.msdn.com/jfoscoding/archive/2006/08/10/695048.aspxFrans ran into some trouble disabling parent menu items. Turns out they dont disable the evaluation of child shortcuts. This was an oversight on our part. That said, most applications remove flyouts that are not in-use so as to not taunt users with menusen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/jfoscoding/archive/2006/08/10/695048.aspx#695155Fri, 11 Aug 2006 10:15:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:695155Frans BoumaThanks! :)http://blogs.msdn.com/jfoscoding/archive/2006/08/10/695048.aspx#695156Fri, 11 Aug 2006 10:15:33 GMT91d46819-8472-40ad-a661-2c78acb4018c:695156Frans BoumaThanks! :) Btw, will this be fixed in the next service pack for .NET 2.0 ?http://blogs.msdn.com/jfoscoding/archive/2006/08/10/695048.aspx#695600Fri, 11 Aug 2006 18:27:36 GMT91d46819-8472-40ad-a661-2c78acb4018c:695600jfoscodingI can't remember - I suspect not.  Behavior like this is tough to change in a service pack - it can wind up breaking existing applications who want the behavior.  Again - sorry for the oversight.http://blogs.msdn.com/jfoscoding/archive/2006/08/10/695048.aspx#701064Tue, 15 Aug 2006 15:41:04 GMT91d46819-8472-40ad-a661-2c78acb4018c:701064Bonski's BoxFrans Bouma (recently) discovered that menuitems inside a flyout/popup menu are still accessible eventhough