From: Steve K. <ha...@ya...> - 2006-07-19 22:31:14
|
I think it's ok. This is one of the overridden functions where the function call doesn't take the input wxArrayString, but rather returns the array as a lua table. // %override [unsigned int, lua string table] wxDir::GetAllFiles(const wxString& dirname, const wxString& filespec = "", int flags = wxDIR_DEFAULT) My apology, it is just that I read the un commented line %wxchkver23 static unsigned int GetAllFiles(const wxString& dirname, wxArrayString *files, const wxString& filespec = "", int flags = wxDIR_DEFAULT) and still think that the method is still using *files its argument so I still pass dummy args into it and it failled, then whining about it :-). I should look at the override line . I have been wondering if it might be simpler to use wxArrayString for these cases rather than returning a lua table of strings. You can always use the added function wxArrayString:ToLuaTable() to get it as a table if you like. What do you think? On one hand it's nice to use the native lua table for arrays like this, but on the other hand the bindings are easier with fewer overrides and confusion with the wxWidgets docs if we keep it as a wxArrayString. I personally prefer lua table; as I can get it out, process it using lua code etc. It is just much easier to use lua then , my memory is not good, and lots of time I have to open wx docs to find a method name etc.. but I can not forget : for i,v in pairs(bla) do :-) end Cheers, S.KIEU --------------------------------- Do you Yahoo!? Yahoo! Personals: It's free to check out our great singles! |