http://joel.neubeck.net/2009/02/tip-dont-be-scared-to-use-xname-in-xaml/ Simplifing structure without changing results Sat, 06 Feb 2010 06:09:02 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://joel.neubeck.net/2009/02/tip-dont-be-scared-to-use-xname-in-xaml/comment-page-1/#comment-759 Jeremy Wed, 18 Feb 2009 19:42:38 +0000 http://joel.neubeck.net/?p=336#comment-759 This is an excellent suggestion! I have often wanted to have dynamic keyframe values! This is an excellent suggestion! I have often wanted to have dynamic keyframe values!

]]> http://joel.neubeck.net/2009/02/tip-dont-be-scared-to-use-xname-in-xaml/comment-page-1/#comment-758 joel Wed, 18 Feb 2009 15:59:48 +0000 http://joel.neubeck.net/?p=336#comment-758 I think you have to be selective since it is creating a private references for each named element. I have seen complex user controls, such as vector sprites in a game with tons of named path's, that have thousands of references on the stack. If your not going to need it in code behind then you don't need to give it a x:Name. I think you have to be selective since it is creating a private references for each named element. I have seen complex user controls, such as vector sprites in a game with tons of named path’s, that have thousands of references on the stack. If your not going to need it in code behind then you don’t need to give it a x:Name.

]]> http://joel.neubeck.net/2009/02/tip-dont-be-scared-to-use-xname-in-xaml/comment-page-1/#comment-757 Corey Schuman Wed, 18 Feb 2009 03:13:06 +0000 http://joel.neubeck.net/?p=336#comment-757 Here here. I believe x:Name should be specified for all elements. It forces you to make sure each element has a purpose. Sure, sometimes it's a pain but once you're use to it you won't regret it. Here here. I believe x:Name should be specified for all elements. It forces you to make sure each element has a purpose. Sure, sometimes it’s a pain but once you’re use to it you won’t regret it.

]]>