I had stopped using the PyWin debugger, back in 2.3, because of numerous problems, and unexpected things happening.Now, in 2.4.3 I had tried ti again, but still have the same old problems.I have a script which justs iterates through text files, countng lines, and functions, and subs, of another
to be objects, and that's another place where I went wrong.Will change my variants to Objects.
On 12/8/05, Tony C [EMAIL PROTECTED] wrote:
Your main problem is that you forgot the self param in the method.
Actually, I started out *with* the self as described in the book.I removed it because the error message
Ok, I'm about 90% there nowI've used the Simple.py from page 213, because there is less involved.when I run it- I see the registration messages. All is good so far.I made one tiny change, related to the call to CreateGuid()
import pythoncomclass PythonCOMServer: _public_methods_ = ['pyCOMSplit']
I would think a better approach would be to instantiate multiple instances like this.
Have you tried something like this?
lv1 = win32com.client.Dispatch(LabVIEW.Application)
lv2 = win32com.client.Dispatch(LabVIEW.Application)
hi,
anybody has called two VIs in parallel??
somehow like this:
Message: 8
Date: Mon, 21 Mar 2005 17:58:50 +0100
From: magic joe [EMAIL PROTECTED]
Subject: [python-win32] screenshot of a window?
To: python-win32@python.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; format=flowed; charset=iso-8859-1;
reply-type=original
Make the window you
When I tried accessing a COM server using win32com.Dispatch() , only
the first command sent to the COM server would work after dispatching
it, then all susequent calles to the Execute() method would cause an
excetpion.
Then I read something about EnsureDispatch(), which seems to work 100%
better.
