From 396d4a775dd654629623a9d95a15e2afa8074235 Mon Sep 17 00:00:00 2001 From: jklingen Date: Mon, 19 Dec 2016 21:09:22 +0100 Subject: [PATCH 01/55] text change --- _posts/2016-12-19-our-present-for-you-greenshot-129.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown b/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown index 8819169c4..0b01c4cec 100644 --- a/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown +++ b/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown @@ -8,9 +8,9 @@ tags: - bugfix - release --- -Admittedly, we're a bit early with our gift. But as a piece of software cannot be wrapped and align beautifully with fancy boxes under the tree, we rather hand it over to you right now, so that you can start having fun with the new version before spending time with your beloved friends and family. +Admittedly, we're a bit early with our gift. But as a piece of software cannot be wrapped and aligned beautifully with fancy boxes under the tree, we rather hand it over to you right now, so that you can start having fun with the new version before spending time with your beloved friends and family. -So, what's new in this version? We have improved window screenshots in Windows 10 (which suffered a little cropping in prior versions), also there's an optimization to reduce the problems with uploading to Imgur, which some of you have encountered (actually caused by a per-user rate limiting applied by Imgur). +So, what's new in this version? More than 500 hours of work went into it - we have improved window screenshots in Windows 10 (which suffered a little cropping in prior versions), also there's an optimization to reduce the problems with uploading to Imgur, which some of you have encountered (actually caused by a per-user rate limiting applied by Imgur). If you used to use Greenshot for uploading screenshots to Jira: good news, Greenshot's Jira plugin is now compatible with Jira 7, and a lot faster. It also got some convenient improvements, e.g. it remembers the last viewed issues. From d6ff12b37eb63d014d0e68261dd2ed0a9d855682 Mon Sep 17 00:00:00 2001 From: jklingen Date: Thu, 8 Dec 2016 21:15:32 +0100 Subject: [PATCH 02/55] BUG-2076 fixed broken links to tickets page --- ...013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown | 2 +- ...nstall-earlier-net-versions-when-starting-greenshot.markdown | 2 +- ...09-18-release-candidate-for-greenshot-1-2-available.markdown | 2 +- .../2014-11-11-second-release-candidate-greenshot-1-2.markdown | 2 +- ...-hopefully-last-release-candidate-for-greenshot-1-2.markdown | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown b/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown index e33b3f91c..eabf8ece1 100644 --- a/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown +++ b/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown @@ -15,5 +15,5 @@ tags: []
  • Speaking of .NET: it is well known that applications developed on top of the .NET framework often need some extra memory, this is a trade-off one has to consider. As always, there are pros and contras.

    • By now, you probably have an idea that we have had our share of investigation regarding memory usage, we also have optmized a lot. And you can be sure that we are constantly having an eye on it, looking out for possible room for further improvement, keeping the RAM in mind while changing and adding the code. So, general feature requests like "reduce memory footprint" are not likely to change our way of working, since we care about this anyway :)
    -However, if you have strong indication that Greenshot does not free memory permanently, you should tell us more details about the circumstances. If you encounter a situation which lets memory usage grow more and more after repeatedly doing the same thing, maybe you have actually found a memory leak we are not yet aware of. In these cases, please let us know, including information about your system and an exact description how to reproduce the behavior. We'll have a look at it. +However, if you have strong indication that Greenshot does not free memory permanently, you should tell us more details about the circumstances. If you encounter a situation which lets memory usage grow more and more after repeatedly doing the same thing, maybe you have actually found a memory leak we are not yet aware of. In these cases, please let us know, including information about your system and an exact description how to reproduce the behavior. We'll have a look at it. diff --git a/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown b/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown index e60e0646a..0e03e77e2 100644 --- a/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown +++ b/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown @@ -9,4 +9,4 @@ tags: []

    In case you are using Windows 8, you might see a message when starting Greenshot, saying "An app on your PC needs the following WIndows feature: .NET Framework 3.5 (includes .NET 2.0 and 3.0)". An app on your PC needs the following WIndows feature

    Just skip it. As far as we know, Greenshot is working fine with .NET 4.0.

    Greenshot 1.x is built to run with .NET Framework version 2.0/3.5, and Windows simply does not know that it can be run on .NET 4.0 also, and thus asks whether to install version 3.5.

    -

    If, contrary to expectations, you encounter any errors with this setup, please let us know.

    +

    If, contrary to expectations, you encounter any errors with this setup, please let us know.

    diff --git a/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown b/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown index 90b73f2b5..fca1e4057 100644 --- a/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown +++ b/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown @@ -10,7 +10,7 @@ tags: ---

    We have just uploaded the first release candidate for Greenshot 1.2. It fixes some bugs of the prior version, but, far more important, adds some features that have been requested very often... most notably, the Greenshot 1.2 editor will finally draw speech bubbles / callouts, auto-incrementing labels and offer the possibility to resize the screenshot.

    -

    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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    +

    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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    And, as usal, here is the complete change log - you can download the release candidate (version 1.2.1.2-RC1 - installer, ZIP or PortableApps version) from our version history:

    All details to our tickets can be found here: https://greenshot.atlassian.net

    diff --git a/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown b/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown index d9adea61c..5c360cf08 100644 --- a/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown +++ b/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown @@ -17,7 +17,7 @@ tags:
  • In region mode, the area to capture can now be selected using the keyboard: use arrow keys to move the cursor, then Enter to lock one corner of the region and - after moving the cursors on - hit Enter again at the opposite corner to capture the region

    • See below for the complete changelog of the second release candidate, if you haven't seen the first one yet you might want to have a look at the changelog of RC1, too. In any case, you should check out the new release candidate - as always, it can be downloaded from our version history (1.2.2.43-RC2).

    -

    And, 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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    +

    And, 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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.


    Features:
    * Added the possibility to select the region to capture by using the keyboard, use the cursor keys to move the cursor (ctrl-key speeds up the movement) and the enter key to mark the start and ending.
    diff --git a/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown b/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown index 19f823356..70aea7991 100644 --- a/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown +++ b/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown @@ -13,7 +13,7 @@ tags:

    Most notable improvements are: torn edge and drop shadow settings are now stored and remembered next time, we have also improved the usability of the torn edge settings dialog. In the editor, the font family selection now displays its entries using the respective font so that it is easier to find the font you are looking for.
    We also got rid of several bugs, mostly related to the editor, e.g. the new speech bubble feature still had some flaws.

    See below for the complete changelog of the third release candidate, if you haven't seen the previous ones yet you might want to have a look at the changelog of RC1 and RC2, too. In any case, you should check out the new release candidate - as always, it can be downloaded from our version history (1.2.3.29-RC3).

    -

    Yeah, you know that already, but just to be sure: "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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    +

    Yeah, you know that already, but just to be sure: "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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.


    Features:
    * Greenshot now stores the settings of the torn edge & drop shadow effects
    From 1e2774b871eb04098820ef4bd3809816f6ecb682 Mon Sep 17 00:00:00 2001 From: jklingen Date: Wed, 21 Dec 2016 22:57:57 +0100 Subject: [PATCH 03/55] fixed missing quote in link tag --- ...013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown | 2 +- ...nstall-earlier-net-versions-when-starting-greenshot.markdown | 2 +- ...09-18-release-candidate-for-greenshot-1-2-available.markdown | 2 +- .../2014-11-11-second-release-candidate-greenshot-1-2.markdown | 2 +- ...-hopefully-last-release-candidate-for-greenshot-1-2.markdown | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown b/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown index eabf8ece1..82ae844a2 100644 --- a/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown +++ b/_faqs/2013-02-19-greenshot-uses-x-mb-of-my-ram-why-is-that.markdown @@ -15,5 +15,5 @@ tags: []

  • Speaking of .NET: it is well known that applications developed on top of the .NET framework often need some extra memory, this is a trade-off one has to consider. As always, there are pros and contras.

    • By now, you probably have an idea that we have had our share of investigation regarding memory usage, we also have optmized a lot. And you can be sure that we are constantly having an eye on it, looking out for possible room for further improvement, keeping the RAM in mind while changing and adding the code. So, general feature requests like "reduce memory footprint" are not likely to change our way of working, since we care about this anyway :)
    -However, if you have strong indication that Greenshot does not free memory permanently, you should tell us more details about the circumstances. If you encounter a situation which lets memory usage grow more and more after repeatedly doing the same thing, maybe you have actually found a memory leak we are not yet aware of. In these cases, please let us know, including information about your system and an exact description how to reproduce the behavior. We'll have a look at it. +However, if you have strong indication that Greenshot does not free memory permanently, you should tell us more details about the circumstances. If you encounter a situation which lets memory usage grow more and more after repeatedly doing the same thing, maybe you have actually found a memory leak we are not yet aware of. In these cases, please let us know, including information about your system and an exact description how to reproduce the behavior. We'll have a look at it. diff --git a/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown b/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown index 0e03e77e2..e7c49b749 100644 --- a/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown +++ b/_faqs/2013-10-29-why-does-windows-8-suggest-to-install-earlier-net-versions-when-starting-greenshot.markdown @@ -9,4 +9,4 @@ tags: []

    In case you are using Windows 8, you might see a message when starting Greenshot, saying "An app on your PC needs the following WIndows feature: .NET Framework 3.5 (includes .NET 2.0 and 3.0)". An app on your PC needs the following WIndows feature

    Just skip it. As far as we know, Greenshot is working fine with .NET 4.0.

    Greenshot 1.x is built to run with .NET Framework version 2.0/3.5, and Windows simply does not know that it can be run on .NET 4.0 also, and thus asks whether to install version 3.5.

    -

    If, contrary to expectations, you encounter any errors with this setup, please let us know.

    +

    If, contrary to expectations, you encounter any errors with this setup, please let us know.

    diff --git a/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown b/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown index fca1e4057..d2c3b5f70 100644 --- a/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown +++ b/_posts/2014-09-18-release-candidate-for-greenshot-1-2-available.markdown @@ -10,7 +10,7 @@ tags: ---

    We have just uploaded the first release candidate for Greenshot 1.2. It fixes some bugs of the prior version, but, far more important, adds some features that have been requested very often... most notably, the Greenshot 1.2 editor will finally draw speech bubbles / callouts, auto-incrementing labels and offer the possibility to resize the screenshot.

    -

    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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    +

    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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    And, as usal, here is the complete change log - you can download the release candidate (version 1.2.1.2-RC1 - installer, ZIP or PortableApps version) from our version history:

    All details to our tickets can be found here: https://greenshot.atlassian.net

    diff --git a/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown b/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown index 5c360cf08..0418e47bf 100644 --- a/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown +++ b/_posts/2014-11-11-second-release-candidate-greenshot-1-2.markdown @@ -17,7 +17,7 @@ tags:
  • In region mode, the area to capture can now be selected using the keyboard: use arrow keys to move the cursor, then Enter to lock one corner of the region and - after moving the cursors on - hit Enter again at the opposite corner to capture the region

    • See below for the complete changelog of the second release candidate, if you haven't seen the first one yet you might want to have a look at the changelog of RC1, too. In any case, you should check out the new release candidate - as always, it can be downloaded from our version history (1.2.2.43-RC2).

    -

    And, 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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    +

    And, 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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.


    Features:
    * Added the possibility to select the region to capture by using the keyboard, use the cursor keys to move the cursor (ctrl-key speeds up the movement) and the enter key to mark the start and ending.
    diff --git a/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown b/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown index 70aea7991..75043e77a 100644 --- a/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown +++ b/_posts/2014-12-05-third-and-hopefully-last-release-candidate-for-greenshot-1-2.markdown @@ -13,7 +13,7 @@ tags:

    Most notable improvements are: torn edge and drop shadow settings are now stored and remembered next time, we have also improved the usability of the torn edge settings dialog. In the editor, the font family selection now displays its entries using the respective font so that it is easier to find the font you are looking for.
    We also got rid of several bugs, mostly related to the editor, e.g. the new speech bubble feature still had some flaws.

    See below for the complete changelog of the third release candidate, if you haven't seen the previous ones yet you might want to have a look at the changelog of RC1 and RC2, too. In any case, you should check out the new release candidate - as always, it can be downloaded from our version history (1.2.3.29-RC3).

    -

    Yeah, you know that already, but just to be sure: "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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.

    +

    Yeah, you know that already, but just to be sure: "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.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report - thanks a lot.


    Features:
    * Greenshot now stores the settings of the torn edge & drop shadow effects
    From 973283fc5aeff7a21ca4f95deb66e6a2ea515a0c Mon Sep 17 00:00:00 2001 From: jklingen Date: Wed, 21 Dec 2016 23:22:41 +0100 Subject: [PATCH 04/55] Added CSS classes to support image alignments as they were in wordpress posts --- css/main.css | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/css/main.css b/css/main.css index e44fd16e9..4efa96907 100755 --- a/css/main.css +++ b/css/main.css @@ -43,6 +43,16 @@ .clearfix:after { content: " "; display: table; } .clearfix:after { clear: both; } .clearfix { *zoom: 1; } + + /* wordpress theme compatibility */ + img.alignleft { + float: left; + padding: 4px 10px 4px 0; + } + img.alignright { + float: right; + padding: 4px 0 4px 10px; + } /**********************************************/ From a9a53d465b051622ffb165c638a1675de38e3448 Mon Sep 17 00:00:00 2001 From: Robin Date: Sat, 31 Dec 2016 23:36:31 +0100 Subject: [PATCH 05/55] New blog post for 1.2.9.112 and on the thank you site I added a link to the matching blog post (if any), this might improve traffic. --- _includes/version-check.html | 23 ++++++++++- ...important-change-for-picasa-users.markdown | 3 +- ...problems-imgur-upload-performance.markdown | 3 +- ...our-present-for-you-greenshot-129.markdown | 1 + ...appy-newyear-greenshot-129-bugfix.markdown | 38 +++++++++++++++++++ 5 files changed, 62 insertions(+), 6 deletions(-) create mode 100644 _posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown diff --git a/_includes/version-check.html b/_includes/version-check.html index 7d9990da6..5370b0528 100644 --- a/_includes/version-check.html +++ b/_includes/version-check.html @@ -1,9 +1,21 @@ {% assign latest_release = site.github.releases | where:"prerelease",false | where:"draft",false | first %} + + +

    @@ -55,9 +67,16 @@ function compareVersion(a, b) { } var installedVersion = /version=([^&]+)/.exec(location)[1]; -var greenshotTag = {% if latest_release.tag_name %}"{{ latest_release.tag_name }}"{% else %}"Greenshot-Test-1.2.8.12"{% endif %}; +var greenshotTag = {% if latest_release.tag_name %}"{{ latest_release.tag_name }}"{% else %}"Greenshot-Test-1.2.9.112"{% endif %}; var releaseVersion = /.*(\d+\.\d+\.\d+\.\d+)/.exec(greenshotTag)[1]; var compare=compareVersion(releaseVersion, installedVersion); +var matchingBlogPost = release_blog_posts[installedVersion]; +if (matchingBlogPost) { + jQuery('#blog1').prop("href", matchingBlogPost); + jQuery('#blogPost1').slideToggle(); + jQuery('#blog2').prop("href", matchingBlogPost); + jQuery('#blogPost2').slideToggle(); +} if (compare >= 1) { jQuery('#oldVersion').slideToggle(); } else if (compare == 0) { diff --git a/_posts/2015-04-19-new-bugfix-release-with-an-important-change-for-picasa-users.markdown b/_posts/2015-04-19-new-bugfix-release-with-an-important-change-for-picasa-users.markdown index 0b921b638..4a35efdeb 100644 --- a/_posts/2015-04-19-new-bugfix-release-with-an-important-change-for-picasa-users.markdown +++ b/_posts/2015-04-19-new-bugfix-release-with-an-important-change-for-picasa-users.markdown @@ -3,8 +3,7 @@ layout: post status: publish published: true title: ! 'New Bugfix Release with an Important Change for Picasa Users' - - +release_version: 1.2.6.7 tags: - 1.2 - bugfix diff --git a/_posts/2015-11-18-latest-bugfix-release-resolves-problems-imgur-upload-performance.markdown b/_posts/2015-11-18-latest-bugfix-release-resolves-problems-imgur-upload-performance.markdown index dea71fd7c..047c8a660 100644 --- a/_posts/2015-11-18-latest-bugfix-release-resolves-problems-imgur-upload-performance.markdown +++ b/_posts/2015-11-18-latest-bugfix-release-resolves-problems-imgur-upload-performance.markdown @@ -3,8 +3,7 @@ layout: post status: publish published: true title: ! 'Latest bugfix release resolves problems with Imgur upload and performance' - - +release_version: 1.2.8.12 tags: - 1.2 - bugfix diff --git a/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown b/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown index 0b01c4cec..038cc12ec 100644 --- a/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown +++ b/_posts/2016-12-19-our-present-for-you-greenshot-129.markdown @@ -2,6 +2,7 @@ layout: post status: publish published: true +release_version: 1.2.9.103 title: ! 'Our present for you: Greenshot 1.2.9 brings a lot of improvements and fixes' tags: - 1.2 diff --git a/_posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown b/_posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown new file mode 100644 index 000000000..30575b843 --- /dev/null +++ b/_posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown @@ -0,0 +1,38 @@ +--- +layout: post +status: publish +published: true +release_version: 1.2.9.112 +title: ! 'Happy new year: Greenshot 1.2.9 bugfix release' +tags: +- 1.2 +- bugfix +- release +--- +So the year 2016 has come to an end, to celebrate the start of a brand new year we have a little present for you: +We bring you a bugfix release for the bugs found in Greenshot 1.2.9.103 (released at the 19th of december). + +You can see the full changelog below. So just go ahead, [download](/downloads/) the last Greenshot release for 2016 and have a great 2017! + +Yours with best wishes for 2017, + +the Greenshot team + + +*Release notes for Greenshot 1.2.9.112-9bc62ac RELEASE* + +|Ticket|Description| +|:-----|:------------| +|[BUG-2065](https://greenshot.atlassian.net/browse/BUG-2065)|OverflowException in the editor| +|[BUG-2077](https://greenshot.atlassian.net/browse/BUG-2077)|It's not possible to disable the update check| +|[BUG-2080](https://greenshot.atlassian.net/browse/BUG-2080)|Exception when opening the context menu| +|[BUG-2089](https://greenshot.atlassian.net/browse/BUG-2089)|Greenshot crashes when hotkey registration fails and OneDrive is not installed| +|[BUG-2091](https://greenshot.atlassian.net/browse/BUG-2091)|Greenshot .zip version has wrong log configuration| +|[FEATURE-992](https://greenshot.atlassian.net/browse/FEATURE-992)|When reusing the editor, it is not brought to the front| +|[FEATURE-995](https://greenshot.atlassian.net/browse/FEATURE-995)|Paste images inside Greenshot editor to the current cursor location| +|[FEATURE-998](https://greenshot.atlassian.net/browse/FEATURE-998)|Opening last capture in explorer should select/jump to the file| +|[FEATURE-1000](https://greenshot.atlassian.net/browse/FEATURE-1000)|Set default focus on the OK-button in the Greenshot quality dialog| + +Translations modified: + +* Nederlands by Stephan Paternotte \ No newline at end of file From 7bd741c67307b4de93ab010392f3593295dbc569 Mon Sep 17 00:00:00 2001 From: Robin Date: Sun, 1 Jan 2017 15:51:20 +0100 Subject: [PATCH 06/55] Improved the blog post of 31.12 a bit. --- ...6-12-31-happy-newyear-greenshot-129-bugfix.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/_posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown b/_posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown index 30575b843..35e6711ff 100644 --- a/_posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown +++ b/_posts/2016-12-31-happy-newyear-greenshot-129-bugfix.markdown @@ -9,13 +9,13 @@ tags: - bugfix - release --- -So the year 2016 has come to an end, to celebrate the start of a brand new year we have a little present for you: -We bring you a bugfix release for the bugs found in Greenshot 1.2.9.103 (released at the 19th of december). +On the 19th of December 2016 we released Greenshot 1.2.9.103 as an early christmas present. +We invested over 500 hours of development time in that version, with that much time there were bound to be a few bugs in there. +Today at the end of the year we bring you a bugfix release, which should solve most reported bugs and even bring a few small features, you can see the full changelog below. -You can see the full changelog below. So just go ahead, [download](/downloads/) the last Greenshot release for 2016 and have a great 2017! - -Yours with best wishes for 2017, +So if you didn't already, just go ahead and [download](/downloads/) 1.2.9.112 the last Greenshot release for the year 2016! +We hope to bring you a lot more Greenshot in 2017 and wish everybody a happy and healthy 2017, the Greenshot team From 9a68fcdac989383c75a4f8c11c00cb902e80a6ec Mon Sep 17 00:00:00 2001 From: jklingen Date: Mon, 2 Jan 2017 21:09:54 +0100 Subject: [PATCH 07/55] Fixed display of prev/next links in blog posts --- css/main.css | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/css/main.css b/css/main.css index 4efa96907..7466c0cac 100755 --- a/css/main.css +++ b/css/main.css @@ -119,6 +119,26 @@ .servicelinks a { color:#666; } + + /* blog prev/next */ + ul.pager { + list-style-type: none; + margin:0; + padding:0; + } + ul.pager i.fa { + font-family: 'FontAwesome' + } + ul.pager li.previous { + display:inline; + } + ul.pager li.next { + display:inline; + float:right + } + ul.pager a { + text-decoration: none; + } @@ -314,4 +334,4 @@ .ad-skyscraper .ad-skyscraper-wrapper { width: 80%; } - } \ No newline at end of file + } From 18a3d2d5af2160dc8bfa522c49ae93cae99701e5 Mon Sep 17 00:00:00 2001 From: jklingen Date: Mon, 2 Jan 2017 21:13:21 +0100 Subject: [PATCH 08/55] CSS reference version bump --- _includes/head.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/head.html b/_includes/head.html index dc588dd70..56e47da18 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -8,7 +8,7 @@ - + {% if page.tags contains "uses_alerts" %} From 29477c0d304365bc81774cfc637f1b2513e2975b Mon Sep 17 00:00:00 2001 From: jklingen Date: Sat, 7 Jan 2017 18:43:54 +0100 Subject: [PATCH 09/55] Alternative ads --- _includes/head.html | 3 + _includes/header.html | 2 +- _layouts/default.html | 6 +- assets/bab-banner.png | Bin 0 -> 16190 bytes assets/bab-skyscraper.png | Bin 0 -> 21140 bytes css/main.css | 10 +- js/main.js | 16 +++ js/vendor/blockadblock.js | 250 ++++++++++++++++++++++++++++++++++++++ 8 files changed, 278 insertions(+), 9 deletions(-) create mode 100644 assets/bab-banner.png create mode 100644 assets/bab-skyscraper.png create mode 100644 js/vendor/blockadblock.js diff --git a/_includes/head.html b/_includes/head.html index 56e47da18..448ed4722 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -22,6 +22,9 @@ + + + diff --git a/_includes/header.html b/_includes/header.html index 3c8b2fd1d..ca60fae66 100644 --- a/_includes/header.html +++ b/_includes/header.html @@ -6,7 +6,7 @@