> Now, reading some other examples included with ActivePython, I realized
> the COM wrapper class generated by makepy is just a mixin. So I tried
> this other approach, inspired by the
> \Python21\Pythonwin\pywin\Demos\ocx\webbrowser.py example included in
> the distribution:
...
> I also noticed when I print rcx.__obj__ that the result is None. As far
> as I understand, the __obj__ attr should point to the COM counterpart of
> my Python class, so it being None must be bad.
__obj__ is the MFC object. _oleobj_ should be the underlying COM object.
> The Activex examples provided with ActivePython assume that the OCX is
> attached to a window. But in this case this would be useless, since I
> have already been able to operate the RCX through Spirit.OCX without any
> GUI. All I need is a way to subclass the Spirit class to implement event
> handlers.
The pywin.demos samples certainly do assume a window, and make use of MFC's
event handling capabilities. They predate the builtin win32com event
handling.
I am afraid I am at the OReilly conference at the moment, so haven't been
following as closely as I would otherwise. I can't recall the problem you
had attempting to use the technique outlined in the docstrings for
win32com.client.DispatchWithEvents(). Can you mail me that info again (no
need to CC the list)
Mark.
_______________________________________________
ActivePython mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/activepython
