AW: Re: SWIG?

> There are some virtual callbacks missing in the wx.NET code, maybe
> this causes the problem. Next wx.NET release will be using swig,
> hopefully we can adress all current bugs/problems with the new
> release.

What are the reason for doing that? I liked the c-library approach
much better than SWIG. There might be some sense in sharing
the SWIG interface with wxPython, but that won't be easy, I assume..

  Robert




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click