Concerning my DnD problem, I'd need to have wxDataObject::GetDataHere
wrapped (at least, dunno if more is needed). It would be really cool if
you could do that, but I think if I want to use wxPython myself, I'll
have to learn SWIG anyway (I want to understand what's going on here).
The README mentions I need to build SWIG 1.1-883 with the patches from
the wxPython sources, but these don't apply cleanly to the mentioned
SWIG version. Now my question is: which SWIG version do you currently
use? Do the patches apply cleanly to this or are additional tricks
needed?
Thanks,
Gerhard
···
--
mail: gerhard <at> bigfoot <dot> de registered Linux user #64239
web: http://www.cs.fhm.edu/~ifw00065/ OpenPGP public key id AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9 3667 814B 9CAA AD24 C930
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))
Concerning my DnD problem, I'd need to have wxDataObject::GetDataHere
wrapped (at least, dunno if more is needed). It would be really cool if
you could do that,
I'll add it to the todo list.
The README mentions I need to build SWIG 1.1-883 with the patches from
the wxPython sources, but these don't apply cleanly to the mentioned
SWIG version. Now my question is: which SWIG version do you currently
use? Do the patches apply cleanly to this or are additional tricks
needed?
I've recently added a patched version of SWIG to CVS as I plan on making a
bunch more changes in the near future. If you get the CVS version of
wxPython sources you'll find it in wxPython/wxSWIG, and setup.py will expect
to find it there too.
BTW, I still need to update all the BUILD.*.txt files to mention the wxswig
and few other changes, but in general they should still be helpful.
···
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!