Cool - does that mean they are fixing it?
Yes, it works with the newest DO 11.3b1
This is by-design - .py files generally aren't axscript files. We
register the .pys extension for this.
Thanks for the information.
Regards,
___
python-win32 ma
On 26/04/2014 8:17 AM, Łukasz Jakubowski wrote:
Hello,
OK, so now the thing is clear (from DO authors):
"""
The actual problem was very simple really - inside Opus the global
script objects were initialised in two steps:
Call the script engine's AddNamedItem method to add the object to its
name
Hello,
OK, so now the thing is clear (from DO authors):
"""
The actual problem was very simple really - inside Opus the global script
objects were initialised in two steps:
Call the script engine's AddNamedItem method to add the object to its
namespace
Add the object to our own internal obj
... and FWIW SetScriptSite seems to get some site:
in 0x05F6A910>._InvokeEx_-SetScriptSite(with obj at 0x04A205D0>,) [1,0,None]
sss site:
Regards,
Hi Mark,
This is the output:
ax.DOpus.OpenOutputWindow()
^
Traceback (most recent call last):
File "
Hi Mark,
This is the output:
ax.DOpus.OpenOutputWindow()
^
Traceback (most recent call last):
File "
That all looks OK. There is a hack in the axscript engine that means
you may be able to use a prefix of 'ax.' - eg, ax.DOpus.OpenOutputWindow()
HTH,
Mark
On 17/04/2014 5:31 AM, Łukasz Jakubowski wrote:
Hello Mark,
This is the output:
# This window will display output from any programs that
Hello Mark,
This is the output:
# This window will display output from any programs that import
win32traceutil
# win32com servers registered with '--debug' are in this category.
Object with win32trace dispatcher created (object=None)
in 0x05932D90>._InvokeEx_-SetScriptSite(with obj at 0x04B3C
Hi Vernon
This system in 32bit XP, so no bitness problems probable.
Regards,
Łukasz
Dnia Tue, 15 Apr 2014 23:14:21 +0200, Vernon D. Cole
napisał:
One other thing to check: are Python and DO11 this same 32 or 64
bit-ness?
32 bit programs cannot talk to 64 bit COM, and vice-versa.
On T
You could try registering the python engine for debugging - change to
win32comext/axscript/client and run "python pyscript.py --debug" - a
message should be printed that the object is registered for debugging.
Then, run "python -m win32traceutil" - this will run a python program
where debug st
One other thing to check: are Python and DO11 this same 32 or 64 bit-ness?
32 bit programs cannot talk to 64 bit COM, and vice-versa.
On Tue, Apr 15, 2014 at 2:49 PM, Łukasz Jakubowski wrote:
> Hi Vernon,
>
> Thanks for the answer.
>
> The DOpus object is not supposed to be created by a user w
Hi Vernon,
Thanks for the answer.
The DOpus object is not supposed to be created by a user with Dispatch (as
DO11 author has told me) - DO11 has no ProgID to use. The object is
brought into script before passing control to it in the same way as fe.
WScript in case of .pys, by calling AddNa
The message means that no one has defined a meaning for the name "DOpus" to
Python.
You, as a programmer, must define that name. If you say:
>>>DOpus = "Spam and Eggs"
then you have defined it as a character string which contains three English
words.
If you say:
>>>from win32com.client import Di
Hello,
I have a problem with a file manager called Directory Opus 11. It supports
ActiveScripting languages, but in case of python, its global objects are
not visible in global namespace.
Python packages (python-3.4.0, pywin32-218.win32-py3.4) seem to be
installed correctly (fe. WS
13 matches
Mail list logo
