win32cliboard behavior

Krzysztof Stachlewski kstc at box43.pl
Tue Oct 8 23:09:15 CEST 2002


"Tim Daneliuk" <tundra at tundraware.com> wrote in message
news:i9avna.lg51.ln at boundary.tundraware.com...

> Well, I discovered the problem (and solution) but I don't understand it.
> Apparently, one must *empty* the clipboard before a write to it
> is globally visible - apparently emptying it is required to "own"
> the clipboard.  Can one of you windows gurus 'splain why this is so?
> I would expect the clipboard to just be readable and writable by everyone...

It is apparently a kind of lock, so noone else can write
into clipboard while you are doing it.

Stach





More information about the Python-list mailing list