## Greenshot 1.1 is available: Introducing the Capture Zoom

You may have noticed that we have been busy with release candidates in the last few weeks. Now, after three release candidates, the few issues that existend seem to be sorted out, so that Greenshot 1.1 is available for download now.

Greenshot 1.1 includes one of the recently most requested features: the new capture zoom is very helpful while selecting a region to capture: it displays a magnified view of the area around the cursor, making it easy to select pixel-exact regions, no matter how tiny they are. The zoom view is flexible enough to stay out of your way as you move the cursor on the screen, but in case you do not want or need it, you can either toggle it off/on easily during capture region selection by hitting the Z key, or disable/enable it in the settings.

Another nice addition is a new output file format called “Greenshot”. When saving a screenshot from the image editor in Greenshot format, you will be able to re-open the file with Greenshot later and have your annotations, shapes etc. still editable.

PortableApps users will be happy to hear that Greenshot is now released for the PortableApps platform, too.

But these are just a few of the new features, there are some more, as well as a lot of bug fixes, extended/improved and/or added translations.

Have a look at the detailed change log entry for Greenshot 1.1 below, or head over to our download page right now to get hold of the new version. We hope you like it as much as we do :)

 1.1.4 build 2622 Release

 Features added: * General: Added zoom when capturing with a option in the settings for disabling the zoom. (this can also be done via the "z" key while capturing.) * General: Better Windows 8 integration: Capture window from list now has the apps and the interactive window capture is not confused by apps or the app launcher. * General: Added Special-Folder support for the OutputPath/Filenames, now one can use the following values: MyPictures, MyMusic, MyDocuments, Personal, Desktop, ApplicationData, LocalApplicationData. Meaning one can now set the output path to e.g. {MyPictures} * General: Greenshot now also comes as a "for PortableApps" download, this now will be released just like the other files (installer & .zip) * Editor: Added a new image format "Greenshot" which allows the user to save the current state and continue editing later. (was already in the 1.1.1.2550) * Editor: The capture is now displayed in the center of the editor, the code for this was supplied by Viktar Karpach. * Editor: Added horizontal and vertical alignment for text boxes. * Printing: Added option to force monochrome (black/white) print * Plug-in: Added Photobucket plugin Bugs resolved (for bug details go to http://sourceforge.net/p/greenshot/bugs and search on the ID): * Bug #1327, #1401 & #1410 : On Windows XP Firefox/java captures are mainly black. This fix should also work with other OS versions and applications. * Bug #1340: Fixed issue with opening a screenshow from the clipboard which was created in a remote desktop * Bug #1375, #1396 & #1397: Exporting captures to Microsoft Office applications give problems when the Office application shows a dialog, this is fixed by displaying a retry dialog with info. * Bug #1375: Exported captures to Powerpoint were displayed cropped, which needed extra actions to correct. * Bug #1378: Picasa-Web uploads didn't have a filename and the filename was shown as "UNSET" in Picasa-Web. * Bug #1380: The window corners on Windows Vista & Windows 7 weren't cut correctly. While fixing this issue, we found some other small bugs which could cause small capture issues on Vista & 7 it also used more resources than needed. * Bug #1386: Resize issues with some the plugin configuration dialogs. * Bug #1390: Elements in 1.0 are drawn differently as in pre 1.0 * Bug #1391: Fixed missing filename in the Editor title * Bug #1414: Pasting captures as HTML-inline in Thunderbird doesn't work when using 256-colors. * Bug #1418: Fixed a problem with the editor initialization, in some small cases this gave an error as something happend at the same time. * Bug #1426: Added some checks for some configuration values, if they were not set this caused an error * Bug #1442: If copying an image from Outlook via the clipboard the image was cropped * Bug #1443: Image exports to Microsoft Word didn't have the "Lock aspect ratio" set * Bug #1444: Colors were disappearing when "Create an 8-bit image if colors are less than 256 while having a > 8 bits image" was turned on * Bug #1462: Auto-filename generation cropping title text after period * Bug #1481: when pasting elements from one editor into another the element could end up outside the visible area * Bug #1484, #1494: External Command plug-in issues. e.g. when clicking edit in the External Command plug-in settings, than cancel, and than edit again an error occured. * Bug #1499: Stability improvements for when Greenshot tries to open the explorer.exe * Bug #1500: Error while dragging an obfuscation * Bug #1504: InvalidCastException when using the brightness-filter * Reported in forum: Fixed a problem with the OCR, it sometimes didn't work. See: http://sourceforge.net/p/greenshot/discussion/676082/thread/31a08c8c * Not reported: Flickr configuration for the Family, Friend & Public wasn't stored. * Not reported: If Greenshot is linked in a Windows startup folder, the "Start with startup" checkbox wasn't checked. * Not reported: Some shortcut keys in the editor didn't respond. * Not reported: Fixed some issues with capturing windows that were larger than the visible screen, logic should now be more reliable. * Not reported: Fixed some cases where Dragging & Dropping an image from a browser on the editor lost transparency. * Not reported: Undo while in an Auto-Crop made the editor unusable. * Not reported: When first selecting a printer, the main printer destination has been replaced by the selected one, making the Windows printer dialog unavailable for further prints * Not reported: Open last capture in explorer doesn't open the right location * Not reported: Fixed some issues where the sub-menus of the context menu moved to the next screen. * Not reported: When having Outlook installed but not the Office plugin there was no EMail destination. ... and more Languages: * Added Indonesian * Installer: Added Spanish * Installer: Added Serbian * Installer: Added Finnish * General: Fixes for many languages  Known issues: * Greenshot general: a captured I-Beam cursor isn't displayed correctly on the final result. * Greenshot general: Not all hotkeys can be changed in the editor. When you want to use e.g. the pause or the Windows key, you will need to be modified the ini directly. * Greenshot general: Can't capture 256 color screens * Greenshot general: Hotkeys don't function when a UAC (elevated) process is active. This we won't change as it is a Windows security measure. * Greenshot general: Capturing apps on Windows 8 when having more than one screen still causes some issues. * Greenshot editor: Rotate only rotates the screenshot, not the added elements or cursor  Posted in Releases | Tagged , , , | Leave a comment ## Getting Closer: Third Release Candidate for Greenshot 1.1 + Indonesian Translation Today we have uploaded the third release candidate for version 1.1. We are very optimistic that this is the last release candidate and that we will release the final version of Greenshot 1.1 very soon. The current release candidate fixes a bug when using the “Highlight Area” feature of the image editor. Furthermore, we are happy to announce a new language in the family of Greenshot translations: Indonesian is included from now on, you can download it for existing installations of previous versions from our downloads page. Thanks a lot to Afif Brika, who created and submitted the translation. By the way: a lot of translations are not up to date with version 1.1 yet. If you would like to enhance an existing translation (or even submit a new language), have a look at this blog post. Thanks :) Enough talk for now, you can download the latest version from our version history page, and here is the changelog:  1.1.3 build 2596 Release Candidate 3  Features added since 1.1.2: * Created a PortableApps version of Greenshot, this now will be released just like the other files (installer & .zip) Bugs resolved (for bug details go to http://sourceforge.net/p/greenshot/bugs and search on the ID): * Bug #1504: InvalidCastException when using the brightness-filter  Languages: * Added Indonesian  Posted in Releases | | Leave a comment ## Release candidate #2 for Greenshot 1.1 is ready for download Just a short notice that we have published the second release candidate for version 1.1 of Greenshot today. It does not only fix bugs reported with the previous release candidate, but also has two additional features: • It is now possible to disable the new zoom window feature for region capture in the settings dialog. • There is a new image format (.greenshot) for saving an edited screenshot, allowing to re-open the file later with annotations etc still being editable. The complete change log can be found below, the latest release candidate is downloadable from our version history page. Check it out and if you encounter an error, please report the bug. Thanks a lot :)  1.1.2 build 2572 Release Candidate 2  Features added since 1.1.1: * Editor: Added a new image format "Greenshot" which allows the user to save the current state and continue editing later. (was already in the 1.1.1.2550) * Capture: Added an option to the settings for disabling the zoom. (this can also be done via the "z" key while capturing.)  Bugs resolved (for bug details go to http://sourceforge.net/p/greenshot/bugs and search on the ID): * Bug #1484, #1494: External Command plug-in issues. e.g. when clicking edit in the External Command plug-in settings, than cancel, and than edit again an error occured. * Bug #1499: Stability improvements for when Greenshot tries to open the explorer.exe * Bug #1500: Error while dragging an obfuscation * Fixed some additional unreported issues  Posted in Releases | Tagged , | Leave a comment ## First release candidate for Greenshot 1.1 It has been a few months since we have released Greenshot 1.0, finally leaving beta status. This was a huge step for us and we are happy to see that the number of downloads is still rising. Greenshot 1.0 has pushed downloads past the 2 million downloads mark last year and it is still downloaded far more than 100.000 times each month. Time to take it to the next level: today we have published the first release candidate for version 1.1 – we decided to keep the interval short, so that you can can benefit from the improvements and new features as early as possible. However, the list of changes and bug fixes is still fairly impressive. Most notable, the region capture mode now comes with a small zoom window, enabling pixel exact selection of the rectangle to capture. But there is a lot more, have a look at the change log below for details. As usual, the disclaimer: “release candidate” means that this version has not gone through extensive testing yet. It might be buggy, so if you do not like surprises, we suggest to stick with version 1.0 until we have ironed out all issues and publish the stable release of version 1.1. And, as usal, here is the complete change log – you can download the release candidate (installer or ZIP) from our version history:  1.1.1 build 2550 Release Candidate 1  Features: * General: Added zoom when capturing * General: Better Windows 8 integration: Capture window from list now has the apps and the interactive window capture is not confused by apps or the app launcher. * General: Added Special-Folder support for the OutputPath/Filenames, now one can use the following values: MyPictures, MyMusic, MyDocuments, Personal, Desktop, ApplicationData, LocalApplicationData. Meaning one can now set the output path to e.g.{MyPictures} * Editor: The capture is now displayed in the center of the editor, the code for this was supplied by Viktar Karpach. * Editor: Added horizontal and vertical alignment for text boxes. * Printing: Added option to force monochrome (black/white) print * Plug-in: Added Photobucket plugin Languages: * Installer: Added Spanish * Installer: Added Serbian * Installer: Added Finnish * General: Fixes for many languages Bugs resolved (for bug details go to http://sourceforge.net/p/greenshot/bugs and search on the ID): * Bug #1327, #1401 & #1410 : On Windows XP Firefox/java captures are mainly black. This fix should also work with other OS versions and applications. * Bug #1340: Fixed issue with opening a screenshow from the clipboard which was created in a remote desktop * Bug #1375, #1396 & #1397: Exporting captures to Microsoft Office applications give problems when the Office application shows a dialog, this is fixed by displaying a retry dialog with info. * Bug #1375: Exported captures to Powerpoint were displayed cropped, which needed extra actions to correct. * Bug #1378: Picasa-Web uploads didn't have a filename and the filename was shown as "UNSET" in Picasa-Web. * Bug #1380: The window corners on Windows Vista & Windows 7 weren't cut correctly. While fixing this issue, we found some other small bugs which could cause small capture issues on Vista & 7 it also used more resources than needed. * Bug #1386: Resize issues with some the plugin configuration dialogs. * Bug #1390: Elements in 1.0 are drawn differently as in pre 1.0 * Bug #1391: Fixed missing filename in the Editor title * Bug #1414: Pasting captures as HTML-inline in Thunderbird doesn't work when using 256-colors. * Bug #1418: Fixed a problem with the editor initialization, in some small cases this gave an error as something happend at the same time. * Bug #1426: Added some checks for some configuration values, if they were not set this caused an error * Bug #1442: If copying an image from Outlook via the clipboard the image was cropped * Bug #1443: Image exports to Microsoft Word didn't have the "Lock aspect ratio" set * Bug #1444: Colors were disappearing when "Create an 8-bit image if colors are less than 256 while having a > 8 bits image" was turned on * Bug #1462: Auto-filename generation cropping title text after period * Bug #1481: when pasting elements from one editor into another the element could end up outside the visible area * Reported in forum: Fixed a problem with the OCR, it sometimes didn't work. See: http://sourceforge.net/p/greenshot/discussion/676082/thread/31a08c8c * Not reported: Flickr configuration for the Family, Friend & Public wasn't stored. * Not reported: If Greenshot is linked in a Windows startup folder, the "Start with startup" checkbox wasn't checked. * Not reported: Some shortcut keys in the editor didn't respond. * Not reported: Fixed some issues with capturing windows that were larger than the visible screen, logic should now be more reliable. * Not reported: Fixed some cases where Dragging & Dropping an image from a browser on the editor lost transparency. * Not reported: Undo while in an Auto-Crop made the editor unusable. * Not reported: When first selecting a printer, the main printer destination has been replaced by the selected one, making the Windows printer dialog unavailable for further prints * Not reported: Open last capture in explorer doesn't open the right location * Not reported: Fixed some issues where the sub-menus of the context menu moved to the next screen. * Not reported: When having Outlook installed but not the Office plugin there was no EMail destination. 

Known issues: * Greenshot general: a captured I-Beam cursor isn't displayed correctly on the final result. * Greenshot general: Not all hotkeys can be changed in the editor. When you want to use e.g. the pause or the Windows key, you will need to be modified the ini directly. * Greenshot general: Can't capture 256 color screens * Greenshot general: Hotkeys don't function when a UAC (elevated) process is active. This we won't change as it is a Windows security measure. * Greenshot general: Capturing apps on Windows 8 when having more than one screen still causes some issues. * Greenshot editor: Rotate only rotates the screenshot, not the added elements or cursor 

## How to send an image to Skype using command line arguments

You may have read our recent blog article about how to connect Greenshot to other desktop applications using the external command plugin.

For most popular software, available command line parameters are well documented, so one can easily find out whether and how it is possible to send an image to it via command line arguments.

In the case of Skype, it takes a bit of investigation to find that out – the list of command line arguments published by Skype is very short, and there is no option listed for sending files to Skype.

However, after having a look at Skype’s context menu integration (when you right click a file in Windows explorer, there is a Skype entry in the “Send to” sub menu) I found out that there is a undocumented command line parameter called SENDTO.

So, actually it is possible to send a file to Skype via command line, and it is as easy as that:
"C:\Program Files (x86)\Skype\Phone\Skype.exe" /sendto: "C:\path\to\image.jpg"
(of course, the path could be different on your computer)

That is good news for us, because if it is possible using command line arguments, of course it is easily possible to do so with Greenshot’s external command plugin as well.
It is easy to configure:

• Right click the Greenshot icon in your systray to bring up Greenshot’s context menu
• Choose the Configure external commands option
• Click the “New” button and fill in the info we have just found out:
Name: Skype
Command: C:\Program Files (x86)\Skype\Phone\Skype.exe (the path might be different on your computer)
Argument: /sendto: "{0}"
• Click “Ok” to save the Skype command configuration
• That’s it: after your next screenshot, the Skype destination will be available in the destination picker or the image editor

## Constructive feedback is always welcome

Dear Greenshot users,

When you encounter problems with Greenshot or need any assistance, we are happy to help out as much as we can. However, to ensure that we can actually be helpful, we kindly ask you to provide the following details with your bug report / support request:

1. Operating system and its version on which you are facing the issue.
2. The version of Greenshot and where you downloaded it, espcially if it wasn’t from getgreenshot.org or sourceforge.net.
3. A detailed description of your problem, what happened, and what did you expect to happen instead, please also include a step-by-step guide how the problem can be reproduced.
4. If you have found a solution (or workaround) for the problem, please update the ticket and tell us (and the other users) about the rescue.
5. Please be polite and patient. We know that it can be nagging if software does not work as expected, but be sure that it isn’t our intention to make this software as annoying as possible for you.

Always keep in mind: the better you describe the problem, the better we can be of help with it. The community will be thankful as well. The information you put down in our tracker might be a great help for other users.

On a side note, Greenshot is not made by a company and we don’t ask money for it or earn money with it.
We develop Greenshot and work on reported bugs/features in our spare time when we don’t work on our regular jobs or have other private obligations; this might sometimes prevent us from helping someone as quickly as we would like. The reason why we make Greenshot is simply that we enjoy writing something that people enjoy using.

As answering every ticket and satisfying everybody takes a lot of time which we would actually rather spend developing new features and fixing bugs (to be honest) we needed to make some rules clear. We are still doing our best to make everybody happy because we believe that it is important to stay in touch with the users in order to develop usable and good software, that’s part of the game.

But please do not take it personally if our replies are slower and kept shorter than what you are used to by professional and commercial 24/7 customer service offices. We just can’t offer that; if we did, Greenshot definitely could not be free. It’s up to you to help us responding to your requests helpfully and with few expenditure of time, by submitting constructive feedback (see list above) and staying polite. And: the less time we spend replying to tickets, the more time we can spend acutually improving this software :)

Please keep these things in mind when getting in touch with bug reports or feature/support requests.

By the way: we will remove the possibility to create and comment tickets anonymously in our bug tracker. On the one hand, this is because there is an increasing amount of spam lately. On the other hand, tickets created anonymously very often lack important information and are not monitored by the creator to reply when we ask for details. These tickets are obviously not helpful to anyone, yet take a lot of our time to process. If you need to get in touch, please register with sourceforge.net or connect with OpenID, it’s quite simple.

Thanks for using Greenshot and taking the time to read this,
the Greenshot development team

## How to use the External Command Plugin to send screenshots to other applications

Ever wondered what is the quickest way to have Greenshot output images to other applications on your PC, e.g. your favorite image manipulation software, upload application or instant messenger?

The Greenshot installer comes with a handy plugin called “External Command Plugin”, allowing Greenshot to output files to a large number of other programs on your computer. E.g. if you prefer Adobe Photoshop or Inkscape for editing your screenshots, it is an easy task to configure custom destinations which you then can select like any other destination. This will work for any program that offers a command line interface accepting an image path.

### What is a command line interface?

A command line interface can be used to send commands to a program, e.g.

explorer.exe C:
will open Windows Explorer and display the contents of your local hard drive C:

copy myfile.txt myfile-2.txt
will create a copy of myfile.txt, creating a new file called myfile-2.txt

mspaint.exe "C:\path\to\image.png"
will open MS Paint to edit image.png located in C:\path\to\ (of course, these are just examples, there’s probably no directory called C:\path\to on your hard drive)

You can execute commands yourself using the Windows command line tool (called cmd.exe)

But you can also configure Greenshot to execute commands like these which comes very handy if you often need to pass your screenshots to other software.

### So how does Greenshot’s External Command Plugin work?

It’s easy… Right click the Greenshot systray icon and click “Configure external commands”.

(If it is not there, you are either using an old version of Greenshot or did not select to install the External Command plugin during the installation process. In both cases, you should download the latest version of Greenshot’s installer and install it. When the installer asks about plugins to install, make sure to check the box next to “External Command Plugin”, and proceed with the installation.)

After doing so, the configuration dialog opens up. For your convenience, we have already added MS Paint to the list (i.e. you can already use it as a screenshot destination from Greenshot’s image editor or destination picker.)
Let’s have a look at its configuration: click “MS Paint” in the list and then the “Edit” button on the right-hand side, you’ll see the configuration options for the MS Paint command:

• Name: how the external command is displayed by Greenshot, you can put in there whatever you like, e.g. MS Paint
• Command: path and file name of the executable program accepting the image, e.g. C:\Windows\System32\mspaint.exe
• Argument: additional information to pass to the program, e.g. "{0}"

In the Argument section {0} will be replaced with the path of the temporary file you are about to export from Greenshot. You should wrap this in double quotes, otherwise it could lead to unexpected behavior if the file name or path contains whitespace characters.

You can close this window. Now that you’ve had a look at the MS Paint command, you’re ready to configure external commands yourself. Simply use the “New” button to add new commands and they will be available in the editor and destination picker.

Please note: not every program offers a command line interface, and arguments are often different than in this example. We (the Greenshot development team) will not be able to offer guidance for working with third party software. Read the other program’s documentation or contact its developers to find out whether and how it is possible to pass an image via command line arguments.

We are very proud to annouce that Greenshot 1.0 is finally available for download now. It has been two years since the last official release and we have not been lazy in the meantime. There have been a lot of bugfixes and performance improvements, but there are also loads of handy new screenshot features coming with Greenshot 1.0, to name just a few of them:

• There’s a nice new feature called “destination picker”, which let’s you choose a target for the screenshot you have just created on the fly
• We have added several plugins for uploading screenshots to image hosting services like Flickr, Picasa, Imgur, and others. There are also plugins for uploading screenshots directly to Jira and Confluence.
• Additional export options e.g. to Microsoft Office programs, and the ability to add custom commands to other software using the External Command Plugin.
• A lot of changes making installation of Greenshot in a corporate environment easier for the system administrators, offering silent installation and the possibility to provide a default configuration while installing.

But that’s just a small part of a really huge list of changes. Have a look at the change log at the end of this post.

For those of you that are already using Windows 8: we are able to test with it and have been testing the current relase against Windows 8. Currently Greenshot works, as far as we noticed, as designed when using the normal desktop and can capture the Metro “view” with the region or screen capture. It’s not (yet) possible to select Metro applications via the context menu or use the interactive windows capture.

Greenshot started off as a very simple tool more than five years ago and has been in beta stadium since then. Over these years, more than 2.000.000 downloads have been recorded from Sourceforge’s download servers alone, not even taking into account the numerous software portals that are redistributing different versions of Greenshot (*), recently that’s more than 20.000 downloads every week.
Today Greenshot is a feature-rich (yet simple to use) screenshot tool and the current version is not only the best-featured Greenshot release ever, but also the most stable one. Time to get rid of the odd “beta” label With the help of many friendly users we have ironed out a lot of bugs of the previous versions, added a lot of cool new features, improved old features; and not to forget: we are able to offer Greenshot in 32 languages at the time of this writing. Thanks to the supporters all around the world who helped us to make Greenshot what it is today.

Now go ahead and download Greenshot 1.0 and have fun with the new features. We hope that you like the new version as much as we do

*) By the way: we strongly recommend to always download Greenshot from our official website http://getgreenshot.org/ – there have been reports about some (even popular) software portals offering wrapped installers of open source projects, bundling adware or even malware with the original installer. Also the installers for download are often outdated or “nightly builds” which might be buggy and are not intended to be used by a wide audience.

We have just uploaded the fifth release candidate for Greenshot 1.0 – the new version contains a few bugfixes, for details have a look at the changelog at the end of this entry.

As always, please give us feedback if you have any problems. We are confident that (unless a serious bug is found in this release candidate) we will be ready for the final release of Greenshot 1.0 within the next few days. We are looking forward to this :)

For those of you that are already using Windows 8: we already did some testing with the current release candidate; we noticed that the installation process (during the optimzation phase) takes slightly longer than we are used to, but this might just be the case because if it is the first .NET application to be installed on a fresh Windows 8 system. So don’t be surprised if the installer seems to do a slower job.

And here is the changelog:

 1.0.5 build #### Release Candidate 5

 

Bugs resolved * Fixed translation issue in expert settings, clipboard format options not being updated right away after switching UI language, see bug #3576073 * Fixed bug #3578392: one of the clipboard formats we generate doesn't support transparency, but we forgot to remove it. * Fixed a bug that prevented the clipboard formats to represent the general output settings. (decrease colors if possible etc) * Fixed a bug that the context menu was shown 2x, it's not really visible but does not improve the performance. * Fixed a bug when capturung a minimized IE window, now we first restore it (un-minimize) before capturing. 

## Release Candidate #4 is available

Well, that one was short-lived ;-)
The third release candidate (released only yesterday) introduced two annoying bugs regarding several upload plugins (OAuth authentication process was broken) and the external command plugin (not working).
Those are fixed now, and the fourth release candidate is now available on our version history.

Here are the release notes:
 1.0.4 build 2176 Release Candidate 4

 

Bugs resolved: * Fixed error during OAuth process due to authorization dialog not opening, see bug #3578480 * Fixed error in external command plugin, see bugs #3578391, #3578379, #3578377 * Fixed editor window not being resized to image size, see bug #3578325