This didn't get answered on the PyCrust list, so I thought I'd bump it up
to the wxPython list.
···
---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."
-----Original Message-----
From: pycrust-users-admin@lists.sourceforge.net
[mailto:pycrust-users-admin@lists.sourceforge.net]On Behalf Of Patrick K.
O'Brien
Sent: Wednesday, November 14, 2001 5:01 PM
To: Robin Dunn; Pycrust-Users
Subject: RE: [PyCrust] clipboard destroyed on program exit
Is there any way to force wxPython to put the data on the clipboard, rather
than just a promise? This seems like something that should be decided by
each application, no?
---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."
-----Original Message-----
From: pycrust-users-admin@lists.sourceforge.net
[mailto:pycrust-users-admin@lists.sourceforge.net]On Behalf Of Robin Dunn
Sent: Monday, November 12, 2001 10:09 AM
To: Pycrust-Users
Subject: Re: [PyCrust] clipboard destroyed on program exit
I believe wxWindows uses the promise method.
--Robin
Kevin:
Patrick thought I should bring this up here to see if Neil or Robin have
any ideas what causes this? Is there something in wxPython or
Scintilla that is messing with the clipboard when the app exits? I've
never seen this issue when copying text from a wxTextCtrl and
then exiting an app, it only happens with the PyCrust shell.
This is on Windows? On X/Linux this is hard to fix as you only provide
'promises' (in Mac terms) of your clipboard value. Then when another app
wants to paste, you are sent a message and you provide the full contents of
the clipboard. On Windows, you can either provide promises or data. The
reason for promises is the cost in rendering and storing the selection in
all possibly required formats when processing the copy/cut commands.
Because
of this deep platform difference (and even worse, the asynchrony required
on
X), Scintilla leaves it up to the platform adaptation layer to handle
clipboard operations. So it is up to Robin 
Neil