> I've encountered a problem when trying to use Com in some
> instances. There is a
> method on a Com object called getData() which takes in 4
> paramaters ... all
> pointers ... and fills them with data. I'm currently using
> pointer() in ctypes on
> the four args as they go in (like getData(point
> static PyObject *my_callback = NULL;
> PyMODINIT_FUNC my_set_callback(PyObject *args)
> {
> PyObject *temp = args;
> Py_XINCREF(temp); /* Add a reference to new callback */
> Py_XDECREF(my_callback); /* Dispose of previous callback */
> my_callback =
Tim Roberts <[EMAIL PROTECTED]> writes:
> So, you're from that OTHER OSU? (From an Oregon State University
> alumnus...)
and, don't forget about that other other OSU, Oklahoma State. :-)
> Google is your friend. WS_EX_TOOLWINDOW is used to create floating
> toolbars, which can exist outside
Hello List,
I've encountered a problem when trying to use Com in some instances. There is a
method on a Com object called getData() which takes in 4 paramaters ... all
pointers ... and fills them with data. I'm currently using pointer() in ctypes
on
the four args as they go in (like getData(point
On Tue, 09 Aug 2005 09:17:24 -0400, Benjamin Rutt <[EMAIL PROTECTED]> wrote:
>Benjamin Rutt <[EMAIL PROTECTED]> writes:
>
>
So, you're from that OTHER OSU? (From an Oregon State University
alumnus...)
>-
>from win32g
Hello guys, Im still implementing my callback to python from my dll and the python interpreter crashes
I have no idea atm why
I use the calldll module for calling my c++-dll from my module calldllsound.py:
import calldll
import struct
class CallSoundDLL:
def __init__(self, library):
