github/greenshot
1
0
Fork 0
mirror of https://github.com/greenshot/greenshot synced 2025-08-21 22:13:23 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated some FAQ entries, and made some fixes to our most recent post

Browse source
This commit is contained in:
Robin 2017-02-04 21:55:08 +01:00
commit 0728a3f179
5 changed files with 92 additions and 75 deletions
Download patch file Download diff file Expand all files Collapse all files

65
_faqs/2013-04-16-what-is-the-best-way-to-control-greenshots-configuration-at-install-time.markdown
View file

@ -8,21 +8,50 @@ permalink: /faq/what-is-the-best-way-to-control-greenshots-configuration-at-inst
tags: []
---
<p>Greenshot offers several mechanisms for better control over its configuration, especially useful when deploying Greenshot to several computers, e.g. roll-out in a company.</p>
<p>Greenshot looks for config files in the following locations (and accepts the first location it finds a config file in):</p>
<ol>
<li>installation directory (where Greenshot.exe is located)</li>
<li>the executing user's roaming application data directory (e.g. <code>C:\Users\USERNAME\AppData\Roaming\Greenshot\</code>)</li>
</ol>
<p>There may be three files to control the configuration, each one of them may have all or a subset of the configuration parameters Greenshot offers. The files are loaded in the following order, each one overwriting the configuration parameters of the previous (if set):</p>
<ol>
<li>greenshot-defaults.ini</li>
<li>greenshot.ini</li>
<li>greenshot-fixed.ini</li>
</ol>
<p>Use <strong>greenshot-defaults.ini</strong> to provide your users with a common default configuration, e.g. where files should be stored or whether Greenshot should check for newer versions.<br />
<strong>greenshot.ini</strong> is used by Greenshot to store any settings changed by the user.<br />
Use<strong>greenshot-fixed.ini</strong> to force a set of configuration settings whenever Greenshot starts up. E.g. you might want to ensure that all users use the grayscale option for printing. This file is loaded last, so specifying a setting in here will overwrite the same setting (if present) from the previous files. In most cases fixed settings can also not be changed in Greenshot's settings dialog. If a user succeeds in changing the configuration manually, it will be overwritten again when Greenshot is started next time.</p>
<p>Greenshot will not modify greenshot-defaults.ini or greenshot-fixed.ini. If greenshot.ini is not found in both locations, it will be created automatically in the roaming application data directory, the configuration will then be aggregated from Greenshot's default configuration and greenshot-defaults.ini/greenshot-fixed.ini (if present).</p>
<p><strong>See also:</strong><br />
<a href="/faq/where-does-greenshot-store-its-configuration-settings/" title="Where does Greenshot store its configuration settings?">Where does Greenshot store its configuration settings?</a></p>
This documentation will help you if want to have more control over Greenshots configuration, for instance to pre-set a language or specifiy settings for your companies JIRA/Confluence server.
Except for the functionality that Greenshot is started when Windows starts, all it's settings are stored in [.ini files](https://en.wikipedia.org/wiki/INI_file).
Every added plug-in will has it's own section in the configuration, making sure that developers of plug-in don't need to concern themselves with how the configuration is written.
Greenshot has an intelligent configuration system, and it is readable and even changeable by humans!
To support manual editing the greenshot.ini automatically adds comments to every setting when this is written by Greenshot.
*But if you plan to change something manually, we advice you to stop Greenshot first!!*
If a setting or even a configuration file is missing Greenshot will either take default settings supplied by the developer or a system administrator.
This has the nice advantage that if things no longer work, a setting or the complete configuration can simply be removed.
With our system it's possible to supply specific settings as default, or even make them non changeable.
To understand the possibilities, you first need to know where, how and in what order Greenshot reads it's configuration.
Greenshot knows of 3 different files, which are loaded in the following order:
1. greenshot-defaults.ini: this specifies the defaults which are used if no other setting are available. (At first start)
2. greenshot.ini: this is the normal file, with all the settings of the user, which is written by Greenshot. This overrules the settings in the greenshot-defaults.ini file.
3. greenshot-fixed.ini: has settings which will overrule all settings in the files above.
Greenshot will look for every mentioned file, in the described order, first in the same location as the executable (e.g. installation directory) and if there is not there than in %APPDATA%\Greenshot (e.g. ```C:\Users\USERNAME\AppData\Roaming\Greenshot\```).
The configuration is build from zero, setting for setting, by using the following 4 steps:
1. Take the default set by the developer
2. If a greenshot-defaults.ini was found, and the setting can be found in there, the value from 1 is overwritten.
3. If a greenshot.ini was found, and the setting can be found in there, the value from 2 is overwritten.
4. If a greenshot-fixed.ini was found, and the setting can be found in there, the value from 3 is overwritten.
Greenshot will use the resulting setting, and when every single setting in the complete configuration is processed it will write the complete configuration to it's greenshot.ini file (and only there).
Let's look at a use-case which was asked for a lot of times:
For instance you want to rollout Greenshot in your company and you want to make sure the user doesn't need to select the language (which is asked if nothing was set)?
You can **either** copy a greenshot-defaults.ini, if you want the user to be able to change it, or a greenshot-fixed.ini in the same directory as Greenshot was installed.
To set the default language to Dutch, this file will need to have the following content:
```
[Core]
Language=nl-NL
```
**See also:**
[Where does Greenshot store its configuration settings?](/faq/where-does-greenshot-store-its-configuration-settings/)

55
_faqs/2017-01-29-controling-configuration.markdown
View file

@ -1,55 +0,0 @@
---
layout: faq
status: publish
published: true
title: How can I control Greenshot's configuration during installation and beyond
tags: []
permalink: /faq/how-can-i-control-greenshots-configuration/
---
This documentation will help you if want to have more control over Greenshots configuration, for instance to pre-set a language or specifiy settings for your companies JIRA/Confluence server.
Except for the functionality that Greenshot is started when Windows starts, all it's settings are stored in [.ini files](https://en.wikipedia.org/wiki/INI_file).
Every added plug-in will has it's own section in the configuration, making sure that developers of plug-in don't need to concern themselves with how the configuration is written.
Greenshot has an intelligent configuration system, and it is readable and even changeable by humans!
To support manual editing the greenshot.ini automatically adds comments to every setting when this is written by Greenshot.
*But if you plan to change something manually, we advice you to stop Greenshot first!!*
If a setting or even a configuration file is missing Greenshot will either take default settings supplied by the developer or a system administrator.
This has the nice advantage that if things no longer work, a setting or the complete configuration can simply be removed.
With our system it's possible to supply specific settings as default, or even make them non changeable.
To understand the possibilities, you first need to know where, how and in what order Greenshot reads it's configuration.
Greenshot knows of 3 different files, which are loaded in the following order:
1. greenshot-defaults.ini: this specifies the defaults which are used if no other setting are available. (At first start)
2. greenshot.ini: this is the normal file, with all the settings of the user, which is written by Greenshot. This overrules the settings in the greenshot-defaults.ini file.
3. greenshot-fixed.ini: has settings which will overrule all settings in the files above.
Greenshot will look for every mentioned file, in the described order, first in the same location as the executable (e.g. installation directory) and if there is not there than in %APPDATA%\Greenshot (e.g. ```C:\Users\USERNAME\AppData\Roaming\Greenshot\```).
The configuration is build from zero, setting for setting, by using the following 4 steps:
1. Take the default set by the developer
2. If a greenshot-defaults.ini was found, and the setting can be found in there, the value from 1 is overwritten.
3. If a greenshot.ini was found, and the setting can be found in there, the value from 2 is overwritten.
4. If a greenshot-fixed.ini was found, and the setting can be found in there, the value from 3 is overwritten.
Greenshot will use the resulting setting, and when every single setting in the complete configuration is processed it will write the complete configuration to it's greenshot.ini file (and only there).
Let's look at a use-case which was asked for a lot of times:
For instance you want to rollout Greenshot in your company and you want to make sure the user doesn't need to select the language (which is asked if nothing was set)?
You can **either** copy a greenshot-defaults.ini, if you want the user to be able to change it, or a greenshot-fixed.ini in the same directory as Greenshot was installed.
To set the default language to Dutch, this file will need to have the following content:
```
[Core]
Language=nl-NL
```
**See also:**
[Where does Greenshot store its configuration settings?](/faq/where-does-greenshot-store-its-configuration-settings/)

2
_faqs/2017-01-29-excluding-plugin-destination.markdown
View file

@ -84,4 +84,4 @@ The names of the destinations are a bit harder to find, here is the currently kn
[Where does Greenshot store its configuration settings?](/faq/where-does-greenshot-store-its-configuration-settings/)
[How can I control Greenshot's configuration during installation and beyond?](/faq/how-can-i-control-greenshots-configuration/)
[What is the best way to control Greenshot's configuration at install time?](/faq/what-is-the-best-way-to-control-greenshots-configuration-at-install-time/)

42
_faqs/2017-01-29-keeping-greenshot-clean.markdown Normal file
View file

@ -0,0 +1,42 @@
---
layout: faq
status: publish
published: true
title: What do we do to keep Greenshot clean from malware and viruses
permalink: /faq/is-greenshot-clean/
tags: []
---
Every now and than we get reports of users who have anti-virus software which detects _something_ in Greenshot,
and they are wondering how secure Greenshot actually is.
First, 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.
Athough there is no 100% garantee of building an application which is not infected. We have set a high standard, I would say much higher as some software you must pay for.
The following describes how we work to keep Greenshot clean:
1. Greenshot only contains program code that which we place into our Github Open Source repository, everybody can look into it meaning there are no secrets.
2. Only WE decide what ends up in our repository, and with that what ends into Greenshot, the community can supply us with changes but those are approved by us before moved into Greenshot.
3. Thanks to the nice people at [AppVeyor](https://www.appveyor.com/) Greenshot is build on a clean Windows image, not on our PCs. This has 2 advantages:
* The Windows installation is never used by people and reset every time *before* a build starts. This makes sure that the Windows installation is not infected.
* There is no chance that some modification to Greenshot, which is on our system but not pushed to github, ends up in our product.
4. We check Greenshot with [Virus Total](https://www.virustotal.com/) before we make it available to the public
5. We sign our product with a code signing certificate, since 1.2.9, so people can detect if someone tampered with the files.
So, as long as you download via *our* [site](https://getgreenshot.org/downloads) you should be fine.
About those people who reported that their anti-virus software detected something, upto now I think we did our work as:
* some never replied back to our question from *where* they downloaded Greenshot.
* some downloaded Greenshot from elsewhere, not from our site.
* the others were identified as false positives.
**See also:**
[Promised: No Bundled Installers, No Toolbars, No Unfair Advertisements](/2013/11/19/promised-no-bundled-installers-no-toolbars-no-unfair-advertisements/)

3
_posts/2017-01-28-129-january-bug-bash.markdown
View file

@ -12,7 +12,7 @@ tags:
Good news everyone!
Today we present you the result of our January Greenshot [Bug Bash](https://en.wikipedia.org/wiki/Bug_bash).
In 28 days we fixed 24 bugs, to make this possible we invested around 60 hours of development time.
During this bug bash we fixed 24 bugs, to make this possible we worked around 18 after work evenings and three weekends (in 28 days).
We would like to thank all people for taking time to report bugs, without we wouldn't be able to know about them.
Especially the people who reported bugs and were available for questions & testing have
our utmost gratitude, without them we would not haven been able to fix this amount of bugs in such a short time.
@ -26,6 +26,7 @@ Some special notes for people coming from Greenshot 1.2.8 (or older):
* To make it possible to keep using the Jira plug-in we used code which was due in Greenshot 2.0, this is why **the Jira plug-in now needs .NET 4.5**
* We changed the behavior of the effect buttons: left mouse click directly applies and the right mouse click brings up the settings first.
* .greenshot files saved with 1.2.8 (or earlier) cannot be read with 1.2.9, currently there is no workaround for this except to keep with 1.2.8
* With 1.2.9 we changed the windows capture to remove the border, which not everybody likes. This is rolled back with this version, and we need to see how to make this functionality available via a setting.
With this version we added another translation, and reached a total of 37 languages with our latest addition: [Taqbaylit](https://en.wikipedia.org/wiki/Kabyle_language)