From d6ff12b37eb63d014d0e68261dd2ed0a9d855682 Mon Sep 17 00:00:00 2001 From: jklingen Date: Thu, 8 Dec 2016 21:15:32 +0100 Subject: [PATCH] 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