WPF 3.5 SP1 feature: IEditableCollectionView

Link Listing - May 20, 2008

Christopher Steen — Wed, 21 May 2008 15:31:53 GMT

Sharepoint SharePoint Development Conference (FireStarter) at Microsoft on June 11th [Via: Steve Fox...

WPF 3.5 SP1 Feature: Non-live Scrolling

Vincent Sibal's Blog — Thu, 22 May 2008 17:58:52 GMT

So far for the new WPF 3.5 SP1 features, I've surveyed Item Container Recycling , Data Formatting , and

re: WPF 3.5 SP1 feature: IEditableCollectionView

Need Info — Mon, 26 May 2008 11:21:54 GMT

Can u give an example of IEditableCollectionView with GridViewColumn created dynamically with celltemplate.

thx

Using IEditableCollectionView with dynamically generated GridViewColumns

Vincent Sibal's Blog — Wed, 28 May 2008 02:40:15 GMT

I recently got a question on how to implement IEditableCollectionView with GridViewColumns that are dynamically

re: WPF 3.5 SP1 feature: IEditableCollectionView

vinsibal — Wed, 28 May 2008 02:44:21 GMT

Need Info, I just wrote a post on this: http://blogs.msdn.com/vinsibal/archive/2008/05/27/using-ieditablecollectionview-with-dynamically-generated-gridviewcolumns.aspx. Please let me know if you have any other questions.

re: WPF 3.5 SP1 feature: IEditableCollectionView

Need Info — Mon, 09 Jun 2008 17:40:51 GMT

i have a derived class of Listview how can i use NewItemPlaceholderPosition.

in fact i had xamlparsing exception

re: WPF 3.5 SP1 feature: IEditableCollectionView

vinsibal — Mon, 09 Jun 2008 19:08:35 GMT

NewItemPlaceholderPosition is basically the position in the collectionview where a new item will be added. You can specify where you would like to add the new item through the enum.

Can you give me a little more details on the problem that you are having?

re: WPF 3.5 SP1 feature: IEditableCollectionView

Need Info — Wed, 11 Jun 2008 10:52:41 GMT

i have a derived class of Listview and i'm adding dynamically the columns into the gridview.

i'm trying to add the editing capabilities of .net framework 3.5 sp1.

when i'm trying to use NewItemPlaceholderPosition it gives me an xamlparser exception

re: WPF 3.5 SP1 feature: IEditableCollectionView

vinsibal — Fri, 13 Jun 2008 19:07:51 GMT

You're still going to have to be a little more specific on the xamlparser exception and how you are using NewItemPlaceholderPosition.

IEditableCollectionView is implemented by ListCollectionView and BindingListCollectionView. You can set/get this from your derived class by doing something like this,

iecv = (IEditableCollectionView)Items;

iecv.NewItemPlaceholderPosition...

It is not a DP so you cannot use it in xaml like most of the other properties. Maybe you can send me a code snippet and I can be a little more helpful.

Overview of the editing features in the WPF DataGrid

Vincent Sibal's Blog — Wed, 01 Oct 2008 17:55:47 GMT

Introduction I’m going to talk a little on the editing features of the DataGrid. I will dive deep into

re: WPF 3.5 SP1 feature: IEditableCollectionView

Moi — Sat, 03 Jan 2009 21:51:47 GMT

I have a question regarding the IEditableCollectionView as it's implemented for a ListCollectionView. If I have created a ListCollectionView for a collection with a filter, and I call EditItem() on an item that is filtered out, so that it's not part of the collectionview, then calling CommitEdit() will cause an exception.

I would have thought it would be disirable to be able to call EditItem() on any item in the underlying collection, for example if the item is currently filtered out, but we change some data on it, so that it should now be included in the filtered collectionview, currently we have to first check if the item is in the filtered collection view, if it is, we go the EditItem()/CommitEdit() route, if it's not we have to remove it from the collection, modify it and re-add it to the collection to properly refilter this item, it would have been great if we only had to do it in one fashion, ie beeing able to call EditItem()/CommitEdit() on any item in the collection even if it's currently filtered out.

Disired behaviour or just an overlook of the fact that collection can be filtered when creating the current IEditableCollectionView implementation?

re: WPF 3.5 SP1 feature: IEditableCollectionView

vinsibal — Mon, 05 Jan 2009 16:35:43 GMT

Moi,

When you are using a filter on a collectionview, that collectionview will represent only that filtered view now. So what is presented in the presentation layer is the same as the underlying data which makes it more transparent, easier to debug, and more intuitive actually. So this is all by design.

re: WPF 3.5 SP1 feature: IEditableCollectionView

Moshe — Sun, 25 Jan 2009 00:51:58 GMT

I have a question like Moi's...

How would you force the CollectionView to rerun the filter after you've changed the underlying data. The only way I could think of is calling .Refresh()...but doesn't this contradict the idea of IEditableCollectionView?

re: WPF 3.5 SP1 feature: IEditableCollectionView

Tomi Junnila — Thu, 14 May 2009 21:42:53 GMT

Could you describe the exact contract that IEditableCollectionView.AddNew has? Is anything other than creating the new object and adding it to the collection needed?

The reason I'm asking is that I'd need to override the default AddNew in ListCollectionView to create objects of a different type than it otherwise seems to be creating (the types do share an abstract base class). I tried implementing AddNew like described above, and the WPF Toolkit DataGrid I'm using now only allows adding one new item, to the initial NewItemPlaceholder.

re: WPF 3.5 SP1 feature: IEditableCollectionView

vinsibal — Mon, 18 May 2009 17:18:47 GMT

Tomi,

Take a look at this blog post, http://blogs.msdn.com/vinsibal/archive/2008/10/01/overview-of-the-editing-features-in-the-wpf-datagrid.aspx. There is a table showing the contract for IECV.CanAddNew for a ListCollectionView and a BindingListCollectionView.

re: WPF 3.5 SP1 feature: IEditableCollectionView

Rune — Mon, 27 Jul 2009 14:55:50 GMT

vinsibal, I do not think Tomi was interested in CanAddNew.

I have a datasource where adding and deleting rows are expensive operations.

My hope was that I could implement a ListCollectionView descendant and implement the IEditableCollectionView interface myself. No go, it all falls apart rather quickly. (ListCollectionView simply shuts down; http://wpf.codeplex.com/Thread/View.aspx?ThreadId=60656)

What I want is to virtualize the new row until it is committed. I want to create the new row, but keep it as far away from my physical dataset as possible.

At the very least, I need to know when the new item gets committed, so I can update my remote dataset.

PS: The documentation for IEditableCollectionView does not mention IEditableObject with a single word. I am greatful that you spend time educating us, but it would be nice if someone influential could influence the doc-team. ;)

EndEdit()

Rune — Tue, 28 Jul 2009 14:54:32 GMT

Is there a reason why it is not implemented like this:

public void EndEdit()

{

copy = null;

}

or just no code at all... (if you don't want the overhead of creating another instance of copy later)

Seeing as many classes will have to define a blanking method, there should be a good reason why they require every field to be reset rather than just set the instance to null (or do nothing at all).

As I understand it, with LINQ we're supposed to attribute each member with the [Column] attribute. Is there then not enough information for the framework to handle IEditableObject automatically?

re: WPF 3.5 SP1 feature: IEditableCollectionView

vinsibal — Tue, 28 Jul 2009 15:28:00 GMT

Rune,

It could have been implemented by just setting the copy to null. Here is an official example from the doc team, http://msdn.microsoft.com/en-us/library/system.componentmodel.ieditableobject.aspx.

As far as linq question, it may have enough information to handle IEO there but IEO is meant to work for POCOs (plain old CLR objects).

re: WPF 3.5 SP1 feature: IEditableCollectionView

zeekial — Fri, 28 Aug 2009 02:47:09 GMT

When I remove all of the items "Books". Then attempt to add a book the "CanAddnew" flag becomes false and prevents the item from being inserted. These seems like a bug. Do you know of a workaround?