That was the funny thing - no exceptions were raised. But you are right, when running in the UI thread, the collection itself was raising the NotificationCollectionChanged events.
T. From: [email protected] [mailto:[email protected]] On Behalf Of Miguel Madero Sent: Friday, 5 March 2010 9:58 AM To: ozSilverlight Subject: Re: Silverlight ComboBox ItemsSource won't OneWay bind I completely overlooked that, since our ViewModelBase class always does that for us :) Also if your collection implementes INotifyCollectionChanged, I don't think you need to raise property change notifications. If you're raising the CollectionChangsd event on the worker thread, you might have a lot of swallowed exceptions. On Fri, Mar 5, 2010 at 9:49 AM, Tony Wright <[email protected]> wrote: Ok, I have now had a chance to check the code to ensure the property changed event is raised from within the UI thread. It turns out that the event was being raised from within the worker thread, which is wrong. I have now modified the code and tested it, so that the event is raised in the UI thread, and the property is now binding successfully. Thanks for the help. Regards, Tony _______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight -- Miguel A. Madero Reyes www.miguelmadero.com (blog) [email protected]
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
