Have you tried searching CPAN? screenshot

Have you searched CPAN? There are

• Win32::Screenshot
• Imager::Screenshot

#!/usr/local/bin/perl

use strict;
use warnings;

my $file = '/root/Desktop/';
sleep 5;
$file =  system("import -window root MyScreenshot.png");
print $file, "\n";
[download]

use strict;
use warnings;

system("import -window root MyScreenshot.png");
[download]

#!/usr/local/bin/perl

use strict;
use warnings;

my $file = '/root/Desktop/';
sleep 5;
$file =  system("import -window root MyScreenshot.png");
print $file, "\n";
[download]

Ouch! That really hurts my eyes!

• Why do you sleep before taking a screenshot?
• Why do you assign a useless constant to $file?
• Are you sure system() returns a file or a filename? Hint: It doesn't!
• So why do you assign the return value to a variable named $file?
• Why do you mess with the notoriously problematic default shell instead of using the multiple-argument form of system?
• Why do you print the return value of system to STDOUT?

At least, you use strict and warnings.

use strict;
use warnings;

system("import -window root MyScreenshot.png");
[download]

Better, but still problematic: You still invoke the default shell, begging for trouble. All error checks are missing. Yes, system() may fail. For example, because there is no import utility -- e.g. when ImageMagick is not installed. Or because there is some other tool named import, with completely different parameters a and a completely different purpose.

Alexander

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

You still invoke the default shell

Actually, this particular example wouldn't invoke a shell, because there are no shell metacharacters in the command.

$ strace -f -eexecve perl -e 'system("import -window root MyScreenshot
+.png")'
execve("/usr/local/bin/perl", ["perl", "-e", "system(\"import -window 
+root MySc"...], [/* 31 vars */]) = 0
Process 20945 attached (waiting for parent)
Process 20945 resumed (parent 20944 ready)
[pid 20945] execve("/home/almut/bin/import", ["import", "-window", "ro
+ot", "MyScreenshot.png"], [/* 31 vars */]) = -1 ENOENT (No such file 
+or directory)
[pid 20945] execve("/usr/local/sbin/import", ["import", "-window", "ro
+ot", "MyScreenshot.png"], [/* 31 vars */]) = -1 ENOENT (No such file 
+or directory)
[pid 20945] execve("/usr/local/bin/import", ["import", "-window", "roo
+t", "MyScreenshot.png"], [/* 31 vars */]) = -1 ENOENT (No such file o
+r directory)
[pid 20945] execve("/usr/sbin/import", ["import", "-window", "root", "
+MyScreenshot.png"], [/* 31 vars */]) = -1 ENOENT (No such file or dir
+ectory)
[pid 20945] execve("/usr/bin/import", ["import", "-window", "root", "M
+yScreenshot.png"], [/* 31 vars */]) = 0
[download]

As you can see, the import is being run directly.

(Add a ';' (metacharacter) at the end of the command, and it will run the command via a shell...)

murugaperumal

You really need to define the question fully. Perl doesn't have to run on "a screen", so the question is incredibly ambiguous. There are many types of screens, so I couldn't help you even if I wanted to. (Are you running on an X11 terminal? How about Windows? What type of window? Perhaps a serial terminal? Not all of them have a method to save a screen. Perhaps you're running on a teletype? Just rip off the paper and tape it into your document. Maybe it's a web server program? Just provide the appropriate JavaScript to capture the screen and send it back.

If you're going to be a successful programmer, you need to learn to recognize the assumptions you're making. As well as understand the context in which your program runs, and the context in which your client(s) think so you can figure out what the assumptions are. If you can't do that, you need to spend some time practicing on it to be successful. To do so, you might go through all the nouns in your question, and think of their definition. Then think of any possible alternate definitions. When you find alternate definitions, it normally means that you haven't qualified your statement enough to remove the assumption(s). When you're talking with a client, keep in mind that they're normally not going to be a programmer. Each profession has its own terminology/jargon, and you have to verify that what the customer is saying means what you think it means. Frequently a client will use computer jargon incorrectly, and if you don't catch it, you won't be able to fulfill the requirements and waste your time, which will cost you money. Don't be afraid to rephrase statements with different jargon or different examples to verify that the statement means the same thing to both of you, after all, your client wants the correct result as much as you do, and will understand that a little bit of time spent clarifying things will pay off handsomely in the course of the project.

</pedantic_mode>

...roboticus

Perl cannot short out a screen unless there is a electrical problem in your monitor. :)

Now, for a X11 screenshot using Perl and GTK2, use this code: Grabbing that mouse cursor in X11