> The information for wxTheClipboard->SetData say
> "After this function has been called, the clipboard owns
> the data, so do not delete the data explicitly."
>
> And sure enough, as long as the program is running, the clipboard data
> is accessible, but I had expected the wxTheClipboard to function like
> the system clipboard -- to hold a chunk of data without caring about
> that data's originator at all. If I manipulate the clipboard and close
> out a wx program, the clipboard empties itself! This is unexpected
> behavior, to say the least.
It looks like Flush() is what you want, except that it was undocumented until now
(just committed), so I missed it while wrapping wxClipboard... will be in the
next wxPerl version.
> Below is a script which illustrates this behavior. Are my expectations
> out of line?
No, of course :-)
Thanks for the test, anyway
Mattia
>
> use strict;
> use Wx::DND;
|
