in reply to Win32::Clipboard dying?

~~~A lot of LINE NOISE omitted. ~~~ Can anyone point me to the right direction?

Start by editing your post. Add <code>...</code> around the code. You did notice that you posting was hardly readable when you hit the preview button, didn't you?

Then check if and how Win32::Clipboard reports errors. My guess is $!, $@, or $^E. Add that to the message passed to die.

Update: A quick look at Clipboard.xs and Clipboard.pm shows that there is no explicit error handling, so your best bet may be $^E, which hides a call to GetLastError().

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Replies are listed 'Best First'.
Re^2: Win32::Clipboard dying?
by manish.rana@me.com (Initiate) on May 20, 2016 at 00:14 UTC
    Hi afoken, Sorry, that was my first time using the site and I am fairly new at perl. I have edited the post as per your suggestions. The error message is simple the message that I have written after .... or die "No Image Captured".
[reply]
      The error message is simple the message that I have written after .... or die "No Image Captured".

      Read my posting again. I told you where perl hides more information, and that you should write that information somewhere when an error occurs.

      Compare to the usual idiom for opening files:

      open my $f,'<',$filename or die "Can't open $filename: $!";
# ***HINT*** ------------------------------------------^^

      [download]

      Also note that $! will most likely not help you, see my first posting.

      Alexander

      --
      Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
[reply]
[d/l]

In Section Seekers of Perl Wisdom