## Greenshot Switches to JIRA for Bug Reports and Feature Requests

The difference between good and great software often originates from the developers closely listening to the users. As your ideas and comments are valuable input for us, we think that you need be able to easily report bugs and request features, as well as to quickly find information on problems/suggestions that have already been reported by other users.

For a long time, we have used the Sourceforge ticketing system for this, and although it worked for us many years we always thought it wasn’t perfect for our needs. As every member of the Greenshot team also has experience with another ticketing tool, which we all like a lot, it is now time for a change.

We are proud to say we migrated the Greenshot bug/feature tracker to Atlassian Jira, a professional ticketing system. We really think that this improves overall user experience both for us and for you, no matter if you want to report an issue or simply get an overview about what we are up to for the next version of Greenshot. On top of this it is integrated with Atlassian’s BitBucket, where our source code are hosted, which makes it easy to spot what exactly has been changed and why.

Thankfully, Atlassian has a great program to support open source teams with free software services and hosting. We were already using BitBucket and now we introduce Jira, maybe other products follow.

What does this mean for you?

Well, as we hate losing information, we migrated all the current bug reports and feature requests, with the complete history, to our new system. Also all Sourceforge users who reported tickets have been copied to our Jira. The users were created having the same username as with Sourceforge but without a password. At the first login you are asked to reset your password, to make this possible you will receive an email at your Sourceforge account with instructions. After successfully setting your password and being logged in you can change your email address if you like.

Additionally we have been looking for a solution to make it easier and quicker to bring a new version of Greenshot to you, independent of whether we want to build a release or just a version which should solve the bug(s) or add the feature request(s) you reported. For .NET applications this is not easy and as Greenshot is free it shouldn’t cost money, so up to now we have been building Greenshot manually, which was very time intensive and sometimes caused a bit of stress when we forgot something and needed to start all over. Now we finally found an extremely good solution (which is also free for open source projects), and are proud to introduce AppVeyor, a Continuous Integration system for .NET applications, which builds Greenshot for us. The people at AppVeyor really created a great system, it took only a couple of hours to make our build work, and the few questions we had were answered quickly. Although you won’t notice this directly, it does make it possible for us to concentrate on the development so we hope we can fix and extend Greenshot at a quicker pace.

We hope to see you on our new Ticketing system and are looking forward to having a good time while further improving Greenshot together with you.

Posted in Announcements | Tagged , , , | Leave a comment

## Greenshot 1.1.9 Bugfix Release

A new version of Greenshot is available for download, containing bug fixes and small improvements. Most notably, we have

• fixed capture problems that came with a recent update for Windows 8.1, affecting users with multiple displays and different scaling
• repaired upload to Box, which was broken in the previous version
• updated Flickr plugin to be prepared for a breaking change in the Flickr API effective as of June, 27th

Please see the change log below for more details about what’s new. As always, you should make sure to download Greenshot from our download page, rather than being confident in 3rd party download portals to deliver the original version.

 CHANGE LOG:

 1.1.9.13-g01ce82d Windows 8.1 & Box bug-fix Release Bugs resolved: * Bug #1604,#1631,#1634: Capture problems since update to Windows 8.1 with multiple displays * Bug #1627: Box upload failed since 1.1.8 * Unreported: The greenshot.ini values "NoGDICaptureForProduct" and "NoDWMCaptureForProduct" had incorrect defaults, which might cause issues with some applications when using the auto capture mode. Features: * Feature #697: Added the possibility to replace characters/strings when a pattern is used, to have more control over the resulting filename. E.G. \${title:r ,_} will cause all the spaces to be replaced by underscores. * Feature #712: The amount of colour which images are reduce to, if the setting is active, has been made configurable in the greenshot.ini property OutputFileReduceColorsTo. Default stays at 256, * Feature #723: Adding a newline when exporting to Word or an open Outlook email, this makes it possible to repeat exports. Changes: * Flickr plug-in: from June 27th, 2014 Flickr will only accept uploads via HTTPS! As the switch is already possible Greenshot has been changed accordingly. 

Languages: * Updated the French translation for the Microsoft Office plug-in 

Posted in Releases | Tagged , | Leave a comment

## Happy Birthday to Greenshot + New Bugfix Release 1.1.8

Hey, did you know that Greenshot just had it’s seventh anniversary? To celebrate it, we have just uploaded a new release of Greenshot, version 1.1.8. Join the party :)

It mainly consists of bugfixes and small improvements, most notably improved clipboard support, configurable file naming for the Imgur plugin, as well as better readability when editing white or very bright text in the image editor.

As always, you can download the latest stable version from our download page.

For more details, the complete list of changes in Greenshot 1.1.8:

 1.1.8.24-g99facd5 Bugfix Release

 Bugs resolved: * Bug #1578: Changed the behavior of creating filenames for Imgur to be configurable, default will be the date/time. * Bug #1580: removed device names for capture fullscreen submenu in multi-monitor setups, which sometimes delivered inconsistent results or even garbage characters. Sticking to descriptive text like "bottom left", which is more useful anyway. * Bug #1581: Ini-file reading is now done without locking the file, this should help a bit in cases where other applications have this file open. * Bug #1600: Found that Greenshot uses a wrong URL format on the clipboard, this fix might solve some issues * Bug: When capturing client windows on a DWM enabled system (Vista & Windows 7) with "auto" set, sometimes the capture had a blurred/transparent effect. Features: * Feature #663: dark background for textbox input when editing bright-colored text * Feature #667: destinations with subdestinations can now be clicked to invoke the "main" subdestination 

Languages: * Updates for Swedish translation and help, new Swedish translations for plugins and installer * Improvements for German translation and help * Bug #1608: Fixed typo in French translation 

Posted in Releases | Tagged , | Leave a comment

## New Bugfix Release with Important Change for Box.com Users

So here is another release in 2013 – probably the last one ;-) Important especially for those using Greenshot’s Box plugin to send screenshots directly to Box.co. Box.com is applying a breaking change to the authentication API on December 13th, which means that the Box plugin released with Greenshot 1.1.6 will no longer work – we have changed the plugin to work with the new API as of Greenshot 1.1.7.

There are also some bug fixes, especially we got rid of an annoying problem with screenshots being exported to the wrong Word document.
You can read detailed information in the change log below or download Greenshot 1.1.7 right now.

We switched our version control system from Subversion (SVN) to Git and have moved our repository to BitBucket, you can find it here: https://bitbucket.org/greenshot/greenshot/overview
This change makes it easier for other developers to supply patches to our code by sending us pull requests.

 1.1.7.17-g98c8f59 Bugfix Release

 Changes: * We moved our repository to BitBucket (GIT), this forced us to change the build script and the version Bugs resolved (for bug details go to http://sourceforge.net/p/greenshot/bugs and search on the ID): * Bug #1517: (now it is really fixed) export to Microsoft Word always goes to the last active Word instance. * Bug #1589/#1584 System.NullReferenceException * Bug #1574: AccessException when loading plugins 

Features: * Changed the Box plug-in to use the new V2 API, which is mandatory from 13.12.2013. The Box plug-in now needs the .NET 3.5 Full Framework. 

Posted in Releases | Tagged , , | Leave a comment

## Promised: No Bundled Installers, No Toolbars, No Unfair Advertisements

As Greenshot is a free and open source project, we depend on donations and advertising to keep the project running. You probably know that already, since we published a blog post about our thoughts of advertising not so long ago.

Recently, some users told us that bundled stuff like browser toolbars etc. had been installed on their computer by what they assumed was the Greenshot installer, which would have surprised us a lot, since there are no bundled installers or similar annoyances in Greenshot. We are convinced that bundled installers are abusing the user’s trust and therefore we strongly oppose to it, no matter how much money marketing companies pay for them. In dialog with our users and with some research we then found out that these issues actually had nothing to do with our installer at all.

## Unfortunate advertisements on SourceForge and our website

The problem was of another nature: our advertising service (which happens to be the same as SourceForge’s) recently started to deliver advertisements with big green buttons on it, labeled “Download”. The advertised pages do not offer the original Greenshot installer, but other software. However, this fact is not obvious on these pages (probably intended), one of them even offered an executable called Greenshot_Setup.exe.

Of course, we get more ad revenue when advertisements are clicked, but we certainly do not want to trick our users into clicking them accidentally, let alone into installing any other tools than Greenshot.

If this has happened to you: please take our honest apologies, we are very sorry for that. Our advertisements are delivered by Google Adsense, so if you installed anything from their ads, you might want to know that they at least have very strict rules for advertisers.

We are absolutely positive about web advertising to keep web projects going, but we believe ads must be fair and must not impose constraints on visitors.
As a consequence, we have blocked all known advertisers with those unloved “download button ads” from our website and made advertisements even more recognizable by applying a prominent border. We have also gotten in touch with SourceForge asking them to get rid of these ads, too.

## Help us to keep advertisements clean

We can blacklist advertisements we regard unfair or misleading, but of course new advertisements may come in now and then. Also, depending on where you live you might see ads that we will never see over here. Please help us to get rid of them, send uns an email, and don’t forget to include a screenshot of the advertisement and (important) the URL it directs you, otherwise we cannot block it.

## Bundled installers from SourceForge (aka DevShare)

Speaking of SourceForge: lately we got repeatedly approached about bundled installers in SourceForge downloads. There seems to be a big misunderstanding related to this: It is true that SourceForge offers a revenue program called DevShare to projects hosted on their platform, which involves a bundled installer. However, this program is opt-in. As long as the developers of a project do not explicitly choose to take part in DevShare, SourceForge are not bundling anything with the installers.

We, the Greenshot development team, have decided to keep our installer clean, without a doubt, now and in future.

## Further considerations

We are concerned about these alarming flows around free and open source software. This concern mainly relates to practices of reckless people or companies trying to make money on the back of open source projects and their users, but also (to some extend) to the advertising strategy of SourceForge. We are currently considering further steps like moving our installer downloads to another server where we have better control over the ads. Unfortunately, qualititive and reliable Content Delivery Network (CDN) hosting is not cheap.

We are not alone: the developers of the open source image editor GIMP no longer upload their releases to the SourceForge file system; for the sake of completeness and fairness, here is SourceForge’s statement regarding to this discussion.

Posted in Uncategorized | Tagged , , , | Leave a comment

## How to Upload Screenshots to a Web Server via FTP, SCP or SFTP

Ever needed to upload screenshots directly to a server using the FTP, SCP or SFTP protocol? Actually it is quite easy to harness WinSCP’s great scripting capabilities with Greenshot’s flexible external command plugin. This blog post provides a simple WinSCP upload script and explains how to make Greenshot call the script to upload your screenshot.

Sidenote: we know, a specialized plugin for this would be a nice thing to have. A WinSCP plugin is definitely near the top of our todo list, but it probably will not be available before Greenshot 2.0. So in the meantime the following method is a good alternative.

If WinSCP is not installed on your system yet, you can download it from http://winscp.net/, it is free and open source, too.
If you have not heard of Greenshot’s External Command Plugin yet or if you are not familiar with the Windows command line, you might want to have a look at How to use the External Command Plugin to send screenshots to other applications.

## Configuring the upload script

It just needs a few lines to put together a WinSCP script that opens a connection, uploads a single file and closes the connection again – we have prepared a simple script for your convenience. Simply download the WinSCP upload script and store it on your hard disc. Of course, the script needs to know where to upload the files to, so you need to change your the connection settings (in the line starting with open) as well as the target directory on the server (starting with cd).

## Testing the upload script

We recommend to test the script from the command line to see whether everything is alright. You can invoke the script by entering something like this into your command line:
"C:\path\to\WinSCP.com" /script="C:\path\to\winscpupload.txt" /parameter // """C:\path\to\testfile.jpg"""
Of course, C:\path\to\ should reference the path to the files on your local hard disc.

If everything works fine, the script should output something like
 batch abort confirm off Searching for host... Connecting to host... Authenticating... Using username "user". Authenticating with pre-entered password. Authenticated. Starting the session... Reading remote directory... Session started. Active session: [1] user@example.com /remote/path/to/directory/ testfile.jpg | 80 KiB | 37,8 KiB/s | binary | 100% Session 'user@example.com' closed. No session. 

## Configuring Greenshot to call the upload script

The rest is pretty easy:

1. Select “Configure external commands” from Greenshot’s main menu
2. Click the “New” button and enter the following values
3. Name: WinSCP Upload
4. Command: C:\path\to\WinSCP.com
5. Argument: /script="C:\path\to\winscpupload.txt" /parameter // """{0}"""

Take care of the correct syntax, especially the quotes: if there is a space somewhere in a file system path, you need to wrap it into quotes. The last part of “Argument” is literally """{0}""", including the 6 double quotes and curly braces. (Greenshot will replace {0} with the filename of the screenshot.)

That’s it. After confirming the new external command, you can use the WinSCP Upload option for future screenshots, from the destination picker or the editor’s “File” menu.

Posted in How-to | Tagged | Leave a comment

## Greenshot 1.1.6 is ready for download

Not so long ago we have announced that Greenshot 1.1.6 is near, today it is here :)

It includes a few new features/improvements but is mainly a bugfix release, fixing some issues that have been reported for the previous version, especially for those who were having problems with Greenshot “forgetting” their settings now and then and for two problems that occurring when exporting screenshots to Microsoft Office.

The new version is eagerly waiting for you to download it, so don’t keep it waiting and get it from our download page.

Here is the complete changelog for Greenshot 1.1.6 – enjoy :)
 1.1.6 build 2779 Bugfix Release

 Bugs resolved (for bug details go to http://sourceforge.net/p/greenshot/bugs and search on the ID): * Bug #1515: Changed the settings GUI to clearly show that the interactive Window capture mode doesn't use the windows capture mode settings. * Bug #1517: export to Microsoft Word always goes to the last active Word instance. * Bug #1525/#1486: Greenshot looses configuration settings. (At least we hope this is resolved) * Bug #1528: export to Microsoft Excel isn't stored in file, which results in a "red cross" when opening on a different or MUCH later on the same computer. * Bug #1544: EntryPointNotFoundException when using higlight area or blur * Bug #1546: Exception in the editor when using multiple destination, among which the editor, and a picker (e.g. Word) is shown. * Not reported: Canceling Imgur authorization or upload caused an NullPointerReference Features: * Added EXIF orientation support when copying images from the clipboard * Feature #596: Added commandline option "/inidirectory " to specify the location of the greenshot.ini, this can e.g. be used for multi-profiles... * Removed reading the greenshot.ini if it was changed manually outside of Greenshot while it is running, this should increase stability. People should now exit Greenshot before modifying this file manually. 

Improvements: * Printouts are now rotated counter-clockwise instead of clockwise, for most people this should be preferable (#1552) 

Posted in Releases | Tagged , , | Leave a comment

## Current Development Status and Plans for the Future

So what have we been up to? You might have heard little of us, but this doesn’t mean we were sleeping!

Of course we were working on Greenshot 1.1.6, we fixed some mean bugs and even managed to squeeze in a few small features! We will release the new version within the next few days, so stay tuned :)

But mainly we were busy with working on and planning for Greenshot 2.0! We need to make some decisions on how we continue the development, these decisions do not cover which features we are going to develop but rather are important infrastructure changes. When the development of Greenshot started in 2007, .NET Framework 2.0 was used and the target OS was Windows XP. Up till today we didn’t change the .NET framework and still maintain code to support Windows XP, even though none of us has Windows XP anymore, which means that we cannot actually do the testing. You probably know that we are only a small development team, so we cannot support all Windows versions forever… Besides we are missing out on many features that Microsoft offers in newer versions of Windows and the .NET framework which we could use to improve on Greenshot. As .NET framework 2.0 and Windows XP both are getting end of lifed by Microsoft we will no longer be able to use and support these.

Based on these considerations, we decided two things:

• Greenshot 2.0 will be mainly a migration to the newer .NET Framework 4.X and we will remove all special support for Windows Vista and earlier.
• Of course, Greenshot 1.1 will still be available for download. This version works fine on Windows XP and Windows Vista, and we will fix major bugs if they occur, this should be enough for those who bravely stick to the older versions of Windows.

You might ask, “What benefit does this migration bring for me?” Well, we don’t plan many new features for 2.0, but we will be able to enable some hidden and prepared features and improve a lot of the current. As Greenshot was built on a user interface technology that has gotten long in the tooth, adding new settings wasted loads of efforts, which sometimes meant that we didn’t add them in the end. A lot of features, expert or new, were only available by changing the greenshot.ini manually. We are already building a new settings dialog where we can add them quickly and consistent, enhancing usability with an incremental search within the dialog. It is still work in progress, but here is a screenshot to give you an idea:

Finally, this should make it possible for us to improve the Greenshot experience, make the user interface feel more professional and finished.

One thing that does have to wait, is the editor. We have spent a lot of time developing it on the old framework, if we would wait with Greenshot 2.0 before this is migrated to the newer Framework you would have to wait for ages. We rather supply you with smaller treats, so you don’t have to wait so long.

Some other things that we are working on, maybe not so important for most of our users, is the migration our source code from subversion to GIT. This should speed up some of our development and also enable an easier way of helping us out by developing your favorite features yourself. For those that can develop C#, you can create a fork of Greenshot in a few clicks and send us your changes by pull-request (similar to github).

But first of all, we will get Greenshot 1.1.6 ready for you – we will let you know when it is available for download.

Posted in Announcements | Tagged , , , | Leave a comment

## Why a free web needs advertising

First of all: we would like to thank everybody who already donated to Greenshot: thank you so much! Of course, we also appreciate people visiting our website without blocking ads.

Maybe you wonder what we do with your donations and the advertising revenue? Or rather you are asking yourself “What the heck does a piece of code need money for?”. Well, free services and products like Greenshot need financial means to keep going, and unfortunately we aren’t backed by a company that covers our costs. Actually, we need a lot of things to generate this piece of code; our expenses involve costs for hardware, software, electricity, telecommunication, to name just a few… even if these costs wouldn’t exist, we would still work for free, in our spare time. And although we really enjoy developing Greenshot, it’s not just the programming which needs to be done. We spend a large amount of time working on the tickets that are reported (bugs, questions, feature request etc.), social media, coordinating the translations, maintaining this website, etc.

There are mainly two ways to generate at least some income: advertising and donations. Advertising revenue is just as crucial as donations to keep Greenshot running. Unfortunately, ad-blocking software reduces the strength of the advertising pillar. This is the case even if one never clicks any advertisements, since the advertising service we use also pays revenue for displayed ads (of course not as much as for clicks, but every bit helps).

For this reason, if you are using an ad-blocker, we kindly ask you to consider deactivating it on getgreenshot.org and any other websites you like, to support their and our work. We highly appreciate your consideration! To help you make your decision easier: there are no layer ads, interstitials, pop-ups or similar annoyances on our website, we also took care not to mix advertisements with content. And, most important: Greenshot itself is totally ad-free. Just fair, isn’t it?
Just think about paper magazines you might buy regularly: most of them print a considerable amount of ads to keep them going and you still do not get them for free.

If however for some reason you cannot or do not want to stop blocking ads, you might rather want to make a small donation instead?

Thanks for giving this a read and considering action :)

Posted in Uncategorized | Tagged | Leave a comment

## New release with bugfixes and language updates for Greenshot 1.1

Two weeks ago we have published Greenshot 1.1. Just today we have uploaded an updated version (1.1.5), which fixes bugs that have been reported since then – most notably an error message occurring in Windows Vista when trying to apply a drop shadow or torn edge effect to a screenshot, and color prints being printed in grayscale under certain conditions.

We have also received some updates for the translations, which are included in this release: Estonian has been added as a new language (thanks a lot to Olav for submitting the translation), and there are updates for the Ukrainian, Russish, Polish and Italian translation as well.

For all of you interested in more details, read the change log below. Or just download the latest release from our downloads page.

Have fun :)

 1.1.5 build 2643 Bugfix Release

 Bugs resolved (for bug details go to http://sourceforge.net/p/greenshot/bugs and search on the ID): * Bug #1510: Under Windows Vista when trying to apply a drop-shadow or a torn-edge effect a GDIPlus error occurs. * Bug #1512/#1514: Will not print color * Not reported: Annotations where not visible when exporting to Office destinations after writing in the Greenshot format. * Not reported: Removed the update check in Greenshot for PortableApps 

Languages: * New translation: Estonian * Updated translations: Russian, Polish and Italian * New installer translation: Ukrainian * New plugin translations: Polish 

Posted in Releases | Tagged , , , | Leave a comment