wxDataViewCtrl *musicCtrl = new wxDataViewCtrl ( this, wxID_ANY ); wxDataViewModel *musicModel = new MyMusicModel; musicCtrl-> AssociateModel (musicModel); musicModel-> DecRef (); // avoid memory leak !! // add columns now A potentially better way to avoid memory leaks is to use wxObjectDataPtr Typically, you start by setting up the columns (you must have at least one) by calling wxTreeListCtrl::AppendColumn () and then add the items. While only the text of the first column can be specified when adding them, you can use wxTreeListCtrl::SetItemText () to set the text of the other columns. creating a list using wxDataViewCtrl and this works quit well with the exception that it hicks up on date column. I get the following exception: Traceback (most recent call last): Sample data: 2003-10-01 results into 11/07/1238273. So, searched for converting my datetime.date to wxDateTime and found the Using these events is demonstrated in the wxDataViewCtrl sample, although it's limited to the same wxDataViewCtrl, so I'm not sure if they'll be fired when trying to send a wxDataViewItem from one control to another. Thanks for the response, I don't want to get the wxDataViewListCtrl item to wxDataViewTreeCtrl, what I mean by how to get the Provide a method to disable the showing of the root node in wxDataViewCtrl similar to how wxDataViewListCtrl can do this. wxDataViewCtrl requires to show the root node of the view tree yet this is not always what is wanted, for example in the wxDataViewCtrl sample a root node of "My Music" is added that really has no functionality (besides expanding), native controls (at least Mac Osx) provide For example, using/ignoring themes, using/ignoring anti-aliasing, using/ignore cleartype, etc.. I think the issue can be solved by using rectCell instead of rectItem when calling Render when possible. AF> generated for wxDataViewCtrl on MSW It will work if you use dvc->GetMainWindow ()->Bind (wxEVT_LEFT_DOWN). It's unfortunate that GetMainWindow () is not documented, any patches to the docs with Although this works, accessing the main window of wxDataViewCtrl and connecting to the wxEVT_CHAR event feels like a hack to me. So it really might be necessary to add a new event type to wxDataViewCtrl. Something like EVT_DATAVIEW_KEYPRESS which will be sent from the wxDataViewMainWindow::OnChar() handler for keys that are not processed there. If there are a lot of items (more than a couple of thousands) or if it is just more convenient because you already have the data elsewhere, make it virtual. If you need hierarchy too, use wxDataViewCtrl. Of course, all of the above are just the minimal requirements, so you could also use wxDataViewCtrl even if you need just a single column. wxDataViewTreeCtrl. This class is a wxDataViewCtrl which internally uses a wxDataViewTreeStore and forwards most of its API to that class. Additionally, it uses a wxImageList to store a list of icons. The main purpose of this class is to provide a simple upgrade path for code using wxTreeCtrl .