On 2/13/06, k. holwerda <[EMAIL PROTECTED]> wrote:
> It would be great, if you could manage the problem with namespaces in
> wxluacan.
> Or if not so possible, before the release change the namespace to wx
> instead of wxluacan.
> I am confused what is in CVS by now.
Me too, I didn't understand what you meant when you said "run scripts"
when you asked about this before (maybe it wasn't in CVS then?) and
forgot to get back about it. I see that you can do that now.
> But this does not work, when run from the run script menu, it still
> calls function that are wrong.
I've changed wxluacan to use the "wxluacan" namespace and everything
seems to work properly. Please let me know if there are other
problems.
I also changed the interface file and removed %delete for the classes.
It's meant only for classes that lua itself will delete, like wxColour
for example. A wxColour (wxRect etc) exists only in lua and refed
copies of it are passed to c++. You cannot use %delete for a wxWindow
on the other hand since wxWidgets deletes the windows itself so when
lua tries to delete it when being closed you get a segfault. If I
understand correctly the c++ AddObject function takes ownership of the
pointer and deletes it in the destructor.
Regards,
John Labenski
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
