You might try running the dependency walker on
site-packages/win32/win32clipboard.pyd just in case, but I suspect you
won't find anything.
I don't know how...yet :)
win32clipboard.SetClipboardViewer is a function inside of
win32clipboard.pyd, which is a DLL in the Python directory. It,
eventually, calls SetClipboardViewer inside of user32.dll. User32.dll
has been a part of Windows since 1992; I'm 100% confident you'll find
the problem in the Python wrapper somewhere.
On a whim, can you try checksumming the DLL? I'm running pywin32-204.
If you have the same version, you should get the same number:
I'm using pywin32-206. I'm using the exact same python packages on my machine at work
as on my machine a home - I installed it on both PC's using the same files on my USB
thumb drive...So if it is a problem with the dlls, it must have happened *after* I installed it.
I'm not ruling out a virus yet, but that is a strange attack for a virus to follow :-/
Of course it might just be a fluke corruption on one of the files that could only possibly
happen to me because of bad karma and planets being perfectly positioned or something.
I'm going to try a fresh reinstall of all things python tonight. It's very frustrating not to be
able to replicate the error on another machine.
> Is there any way I could have broken the clipboard view chain in a way
> that doesn't fix itself after a restart?
No, that's all in-memory. If it were me, I'd load up Python.exe in a C
debugger and single-step through the function call, but then I'm not
like most people...
*blink blink*. A bit over my head at this time...
I did try the cookbook script here, and it works fine.
As it does with every other machine I've tried it on, and every person on #python that tested it. I can't even
find anything remotely similar to my problem on Google - so chances are it's some freak situation I created
on my PC.
I tried running some clipboard managers at home (Clippy and Clipmagic - both nice programs by the way)
and they don't seem to have a problem recieving the clipboard draw event, so I am sure you are right
about it having nothing to do with the windows dll. It *has* to be in the python wrapper...
Anyway, if my reinstall of python doesn't work - I'll do a reinstall of Windows. A dirty job but somebody has to
do it. If nothing else, it has therapeutic value...fdisk. No compromise.
-d-
_______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
