I realise this list's gone quiet

184 views
Skip to first unread message

Peter O'Hanlon

unread,
Nov 21, 2012, 6:55:22 PM11/21/12
to WPF Disciples
But here's hoping that some are still interested.

Want to do computed observables in WPF? Want a simple way that doesn't involve changing underlying properties? Want something that a simpleton like me could come up with? Try using a MarkupExtension:


--
Peter O'Hanlon

Sachs Barber

unread,
Nov 22, 2012, 2:10:03 AM11/22/12
to wpf-di...@googlegroups.com
Great post pete. Super

Sent from my iPhone

Peter O'Hanlon

unread,
Nov 22, 2012, 3:00:58 AM11/22/12
to wpf-di...@googlegroups.com
Cheers mate.



From: Sachs Barber
Sent: 22/11/2012 07:10
To: wpf-di...@googlegroups.com
Subject: Re: [WPF Disciples] I realise this list's gone quiet

Daniel Vaughan

unread,
Nov 22, 2012, 4:43:12 AM11/22/12
to wpf-di...@googlegroups.com

Terrific article mate! I like the markup extension approach. Top notch.

Peter O'Hanlon

unread,
Nov 22, 2012, 4:48:08 AM11/22/12
to wpf-di...@googlegroups.com
Thanks mate. Unfortunately this won't work with Windows Store apps, but your solution is perfect for that.



From: Daniel Vaughan
Sent: 22/11/2012 09:43
To: wpf-di...@googlegroups.com
Subject: [WPF Disciples] Re: I realise this list's gone quiet

Brian Noyes

unread,
Nov 22, 2012, 7:52:31 AM11/22/12
to wpf-di...@googlegroups.com
Nice!

Hey, let me see if I can hijack the thread with a question that came up from a customer this week. They pointed to this post: http://agsmith.wordpress.com/2008/04/07/propertydescriptor-addvaluechanged-alternative/
Any concerns of a memory leak in the usage of DependencyPropertyDescriptor there?
--
-----------------------------------------
Brian Noyes
Microsoft Regional Director / MVP
+1 703-447-3712
-----------------------------------------

Sacha Barber

unread,
Nov 22, 2012, 8:18:45 AM11/22/12
to wpf-di...@googlegroups.com
Andrews approach is all about be memory leak safe, that is why he uses a Binding rather than using DependencyPropertyDescriptor. I feel its quite safe

Peter O'Hanlon

unread,
Nov 22, 2012, 8:22:11 AM11/22/12
to wpf-di...@googlegroups.com
I'm not sure I get the issue here Brian. As long as you can guarantee that RemovePropertyChanged is called then you should be okay.



From: Brian Noyes
Sent: 22/11/2012 12:52
To: wpf-di...@googlegroups.com
Subject: Re: [WPF Disciples] Re: I realise this list's gone quiet

Brian Noyes

unread,
Nov 22, 2012, 8:37:25 AM11/22/12
to wpf-di...@googlegroups.com
I see, I didn't do a full code walkthrough. I missed that you were calling that and it reminded me of the code I saw the other day that led me to that post by Andrew. Sorry about that!

Peter O'Hanlon

unread,
Nov 22, 2012, 8:40:53 AM11/22/12
to wpf-di...@googlegroups.com
No, it's a good call. The only reason it wouldn't get called in this case is if the DataContext never gets set, and there would be other, bigger problems then.

But thanks for the link. It's an interesting read.



From: Brian Noyes
Sent: 22/11/2012 13:37

Sacha Barber

unread,
Nov 22, 2012, 8:52:50 AM11/22/12
to wpf-di...@googlegroups.com
Ah sorry I thought you were picking holes in Andrews code, which is fine.
--
Sacha Barber
sacha....@gmail.com

Peter O'Hanlon

unread,
Nov 22, 2012, 8:54:57 AM11/22/12
to wpf-di...@googlegroups.com
No, he's picking holes in mine;-)



From: Sacha Barber
Sent: 22/11/2012 13:52

Brian Noyes

unread,
Nov 22, 2012, 9:22:58 AM11/22/12
to wpf-di...@googlegroups.com
<Ducks/>

Sacha Barber

unread,
Nov 22, 2012, 10:05:25 AM11/22/12
to wpf-di...@googlegroups.com
Tis all good
--
Sacha Barber
sacha....@gmail.com
Reply all
Reply to author
Forward
0 new messages