Hi Roee,
Hi Kevin 
Looking at the c++ code, I can see some methods are not implemented yet,
But two of the things I mentioned are bugs:
- Using native listctrl + metal style causes some layout issues (look at the notebook tabs position and the second page’s search ctrl in the attached file).
I’m not seeing any difference between metal and regular style on my machine. (OS X Intel, 10.4.10) I do see a drawing glitch that appears with the default window size and is cleared when resizing, though, but the metal style IIRC does require a bit more spacing between elements to look right.
Did you say you were on Panther, or are you using Tiger as well?
- SetItem disables selection of that item (select the item in the top list in the attached file)
Thanks, this was a stupid bug (a missing check for GetMask() & wxLIST_ITEM_STATE before changing selection state). I also took a moment out to implement GetCountPerPage(), although you’ll have to tell me if it works okay. 
Both fixes will make it into the next release.
btw, any chance the metal extra style will be changed to the new metal look (like the one in the new itunes) ?
Probably not, since they aren’t the same style (you use different commands to set each) and we shouldn’t break apps that still want to use the traditional brushed metal look. We’d need to add an extra style to accommodate this. I actually took a little time out to add a wx.FRAME_EX_UNIFIED (“unified” is the name of the new style, BTW) style and get it working, but I have to get approval from wx devs about this change first before committing.
Thanks,
Kevin
···
On Aug 17, 2007, at 2:24 AM, roee shlomo wrote:
Thanks,
Roee.
On 8/15/07, Kevin Ollivier <kevino@theolliviers.com > wrote:
Hi Roee,
On Aug 15, 2007, at 1:29 AM, roee shlomo wrote:
Hi,
The wxWidgets docs note this:
Mac Note: Starting with 2.8, wxListCtrl uses a native implementation for report mode, and uses a generic implementation for other modes. You can use the generic implementation for report mode as well by setting the mac.listctrl.always_use_generic wxSystemOption to 1.
Sounds like the native wxListCtrl for mac is complete, but:
- The default on wxPython is still the generic widget.
- My tests shows it still has many bugs ( I havn’t tested it deeply, but from how my app behaves with the native list it seems like EVT_LIST_COL_RIGHT_CLICK doesn’t work, GetCountPerPage never returns more than 1, SetStringItem disables the current selection, some size/layout issues…).
My question is:
Is (1) a consequence of (2) and the native listctrl is still work in progress ?
Yes, you can say that, but please report any bugs you find, particularly with a sample app if possible. wxListCtrl is a particularly hard class to code and test, because there are several modes, and it is sometimes very low level. (Whereas on Mac, for example, the native control has a more high-level interface - i.e. you don’t check for column clicks, you receive sort events.) I also, in a number of cases, had no actual working sample of an API (e.g. GetCountPerPage) to test against, making it pretty difficult to know if I’m doing things right, or even how an API is actually used.
There are also a couple cases where wxListCtrl APIs really don’t have a corresponding native API we can use. But in most cases, we were able to find creative solutions, so if you let me know what’s breaking and show me an example of its use, I can probably figure out a way to fix it.
Thanks,
Kevin
–
http://code.google.com/p/lh-abc
<maclistctrltest.py>
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org