Re: Consuming your own events.
Daniel Petersson <[email protected]> Wed, 30 Jan 2008 12:49:49 +0100
| Newsgroups | gmane.comp.windows.devel.dotnet.clr |
|---|---|
| Message-ID | <E8FBCCA96548DD46A1AC748F17EEAD9C0E96F6F4F0@cefalo-mail01.cefalo.local> |
I'm guessing but I assume that Sebastien is refering to the new property store available in WPF. The reason for a new store, instead of fields, is to reduce the memory impact of hundreds/thousands of objects with fields as backing store for all properties. --Daniel ________________________________________ From: Discussion of development on the .NET platform using any managed language [[email protected]] On Behalf Of Sébastien Lorion [[email protected]] Sent: Wednesday, January 30, 2008 12:45 PM To: [email protected] Subject: Re: [DOTNET-CLR] Consuming your own events. On 1/30/08, Sebastien Lambla <[email protected]> wrote: > > When you start, like in WPF, using different property stores for your > events, the problem becomes even worse (and it's that problem that has > triggered my move to this new pattern). Could you elaborate on this bit, I am not sure I follow you. I think you mean to use a hashtable to associate events to their delegate instead of default storage (ie one field by event) ? If so, how is it affected by the OnXXX pattern ? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com