> I thought that maybe the 'mem' driver could be used in conjunction with
pyGTK, but it seems that the 'plsmem' command is missing from the python
bindings.
I looked into this and confirmed that it is indeed missing:
--
.../plplot-5.9.6/buildnmake/bindings/python$ grep 'SWIGINTERN PyObject
\*_wrap' plplotcmodulePYTHON_wrap.c
SWIGINTERN PyObject *_wrap_plshade(PyObject *SWIGUNUSEDPARM(self),
PyObject *args) {
SWIGINTERN PyObject *_wrap_plslabelfunc(PyObject *SWIGUNUSEDPARM(self),
PyObject *args) {
SWIGINTERN PyObject *_wrap_plsmaj(PyObject *SWIGUNUSEDPARM(self), PyObject
*args) {
<----- plsmem should be here!!!! ----
SWIGINTERN PyObject *_wrap_plsmin(PyObject *SWIGUNUSEDPARM(self), PyObject
*args) {
SWIGINTERN PyObject *_wrap_plsori(PyObject *SWIGUNUSEDPARM(self), PyObject
*args) {
--
After some reading about SWIG I have some (minimal) understanding on how
the bindings are automagically generated. It seems likely (to me anyhow)
that the 'void *' in the prototype is causing this function (and others)
to be left out of the bindings.
--
PLDLLIMPEXP void
c_plsmem( PLINT maxx, PLINT maxy, void *plotmem );
--
I found this reference on how to tell swig to skip over such 'issues', but
was unable to get it to work for me:
http://www.swig.org/Doc1.3/Python.html#Python_nn64
Does anyone have any suggestions?
What I am thinking would be useful is that one could create a PIL 'RGB'
object and pass that to plplot, or just pass a contiguous chunk of memory
and then use 'Image.frombuffer' to convert it into a PIL image.
Cheers,
Simon.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Plplot-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-general
