Mark Hammond wrote:
> I'm not sure what could cause this - accidently assigning to
> AttributeError
>
>could possibly cause it, but I can't see any such thing in the code snippet.
>Is that code snippet your *entire* test program?
>
>
>
Yes, the snippet of code was the complete code listing...
> Mark Hammond wrote:
>
> >Try leaving the events class as an "old style" class (ie, don't
> derive from
> >object)
> >
> >
> Hmm.. I did that, and got pretty much the same output - does this stack
> trace help at all? The code listed at the bottom is my complete code
> for my test. I don't need
Mark Hammond wrote:
>Try leaving the events class as an "old style" class (ie, don't derive from
>object)
>
>
Hmm.. I did that, and got pretty much the same output - does this stack
trace help at all? The code listed at the bottom is my complete code
for my test. I don't need anything else
> 1) I wish to be able to use the events available in the object as well,
> and after much reading (and purchasing of your book, Mark - which
> helped ALOT in several other areas - thank you!) I was left feeling a
> bit lost in the 'events' arena. Here is the code I am attempting (short
> and sim
Ok. I have requested and now received a newer version of the OCX
control (from the vendors) that DOES work with VBScript when executed
from wscript/cscript. The PortOpen property now responds correctly
without getting the aforementioned error - and this is a definite
improvement.
However, 2
Mark Hammond wrote:
The same process works fin in _vbscript_ on the example page from
MagTek..
Does it work from _vbscript_ executed via cscript/wscript? If it only works
from _vbscript_ inside a webpage hosting the control, the problem will be that
you need an OCX "containe
> The same process works fin in VBScript on the example page from
> MagTek..
Does it work from VBScript executed via cscript/wscript? If it only works
from VBScript inside a webpage hosting the control, the problem will be that
you need an OCX "container" to host the control. Pythonwin is capabl
