From: John L. <jla...@gm...> - 2006-05-26 16:03:24
|
On 5/25/06, Steve Kieu <ha...@ya...> wrote: > Actually this is needed as I bind some widgets (c++) to wxLua and they have > used such array using the wxWidgets macro; and I would like to access it as > well. > For typical example is the wxArrayTreeItemIds is defined in .i file but > no constructor as well then some third party class used this for the return > value and it is really handy when you want to control the tree; the > wxTreeCtrl understand it rather than the lua table we construct. I have added wxArrayTreeItemIds too. > You are right that most of uses is realy needed to have constructor (you > get the return value from the c++ method ) but sometimes ... > > Of course for all others ; better off using {} :-) I've wondered about this. We can just use the C++ array structures as is, for example wxArrayInt or wxArrayString, but people have made it so that some functions return lua tables of ints or strings instead and I've maintained that. It would be easier for the binder to just return the natural C++ datatype and provide simple functions to convert between the C++ array and a lua table. Do you have any feelings about this? Currently it's a little bit of both, some functions return lua tables others wxArrayXXX. > BTW, the class reference you point is the current CVS version right? I still > _have_ to use the released version though because of some other dependency > to lua 5.0 ; 2.6.2.0; which is still very good to me. That's too bad. The new version really has quite a lot of new and better things. Please don't hesitate to tell us about anything else that's missing or doesn't work though. There's way to much to wxWidgets to test everything and I bet that I use less than 1/4 of the wrappers. Thanks, John Labenski |