Yes, but is it ok that the parameters stay inverted?
wxGrid
SetRowAttr(int row, wxGridCellAttr *attr)
wxGridTableBase
SetRowAttr(wxGridCellAttr *attr, int row)
···
-----Original Message-----
From: Robin Dunn [SMTP:robin@alldunn.com]
Sent: Tuesday, August 21, 2001 2:51 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] Problem in wxGrid grid.i> wxPython 2.3.1, Python 2.1, Win98
>
> Hi
> reading grid.i as a help for wxGrid I found this:
>
> class wxGridCellAttrProvider
> void SetAttr(wxGridCellAttr *attr, int row, int col);
> void SetRowAttr(wxGridCellAttr *attr, int row);
> void SetColAttr(wxGridCellAttr *attr, int col);
>
> class wxGridTableBase : public wxObject
> virtual void SetAttr(wxGridCellAttr* attr, int row, int col);
> virtual void SetRowAttr(wxGridCellAttr *attr, int row);
> virtual void SetColAttr(wxGridCellAttr *attr, int col);
>
> class wxGrid : public wxScrolledWindow
> void SetRowAttr(int row, wxGridCellAttr *attr);
> void SetColAttr(int col, wxGridCellAttr *attr);
>
> I always use wxGrid.SetRowAttr(int row, wxGridCellAttr attr) in Python
so
> I'am not sure if this is a bug or not (rare API at least).The latter are convenience APIs. The grid normally gets/sets attributes
in
the table, which may or may not handle the attributes itself, or it may
just
use a wxGridCellAttrProvider to store the attributes.--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users