2010-07-31 06:52:47 +04:00
|
|
|
#
|
|
|
|
# The Python Imaging Library
|
|
|
|
# $Id$
|
|
|
|
#
|
|
|
|
# screen grabber (windows only)
|
|
|
|
#
|
|
|
|
# History:
|
|
|
|
# 2001-04-26 fl created
|
|
|
|
# 2001-09-17 fl use builtin driver, if present
|
|
|
|
# 2002-11-19 fl added grabclipboard support
|
|
|
|
#
|
|
|
|
# Copyright (c) 2001-2002 by Secret Labs AB
|
|
|
|
# Copyright (c) 2001-2002 by Fredrik Lundh
|
|
|
|
#
|
|
|
|
# See the README file for information on usage and redistribution.
|
|
|
|
#
|
|
|
|
|
2012-10-16 06:49:13 +04:00
|
|
|
from . import Image
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# (New in 1.1.3) The <b>ImageGrab</b> module can be used to copy
|
|
|
|
# the contents of the screen to a PIL image memory.
|
|
|
|
# <p>
|
|
|
|
# The current version works on Windows only.</p>
|
|
|
|
#
|
|
|
|
# @since 1.1.3
|
|
|
|
##
|
|
|
|
|
|
|
|
try:
|
|
|
|
# built-in driver (1.1.3 and later)
|
|
|
|
grabber = Image.core.grabscreen
|
|
|
|
except AttributeError:
|
|
|
|
# stand-alone driver (pil plus)
|
|
|
|
import _grabscreen
|
|
|
|
grabber = _grabscreen.grab
|
|
|
|
|
|
|
|
##
|
|
|
|
# (New in 1.1.3) Take a snapshot of the screen. The pixels inside the
|
|
|
|
# bounding box are returned as an "RGB" image. If the bounding box is
|
|
|
|
# omitted, the entire screen is copied.
|
|
|
|
#
|
|
|
|
# @param bbox What region to copy. Default is the entire screen.
|
|
|
|
# @return An image
|
|
|
|
# @since 1.1.3
|
|
|
|
|
|
|
|
def grab(bbox=None):
|
|
|
|
size, data = grabber()
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
im = Image.frombytes(
|
2010-07-31 06:52:47 +04:00
|
|
|
"RGB", size, data,
|
|
|
|
# RGB, 32-bit line padding, origo in lower left corner
|
|
|
|
"raw", "BGR", (size[0]*3 + 3) & -4, -1
|
|
|
|
)
|
|
|
|
if bbox:
|
|
|
|
im = im.crop(bbox)
|
|
|
|
return im
|
|
|
|
|
|
|
|
##
|
|
|
|
# (New in 1.1.4) Take a snapshot of the clipboard image, if any.
|
|
|
|
#
|
|
|
|
# @return An image, a list of filenames, or None if the clipboard does
|
|
|
|
# not contain image data or filenames. Note that if a list is
|
|
|
|
# returned, the filenames may not represent image files.
|
|
|
|
# @since 1.1.4
|
|
|
|
|
|
|
|
def grabclipboard():
|
|
|
|
debug = 0 # temporary interface
|
|
|
|
data = Image.core.grabclipboard(debug)
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
if isinstance(data, bytes):
|
2012-10-16 06:49:13 +04:00
|
|
|
from . import BmpImagePlugin
|
2012-10-17 07:01:19 +04:00
|
|
|
import io
|
|
|
|
return BmpImagePlugin.DibImageFile(io.BytesIO(data))
|
2010-07-31 06:52:47 +04:00
|
|
|
return data
|