mirror of
https://github.com/greenshot/greenshot
synced 2025-08-22 14:24:43 -07:00
Added two new FAQ entries.
This commit is contained in:
Robin
parent
d48da2f507
commit
721e62d29c
2 changed files with 142 additions and 0 deletions
55
_faqs/2017-01-29-controling-configuration.markdown
Normal file
55
_faqs/2017-01-29-controling-configuration.markdown
Normal file
|
|
@ -0,0 +1,55 @@
|
|||
---
|
||||
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/)
|
||||
87
_faqs/2017-01-29-excluding-plugin-destination.markdown
Normal file
87
_faqs/2017-01-29-excluding-plugin-destination.markdown
Normal file
|
|
@ -0,0 +1,87 @@
|
|||
---
|
||||
layout: faq
|
||||
status: publish
|
||||
published: true
|
||||
title: How can I remove plugins or destinations from Greenshot?
|
||||
permalink: /faq/how-remove-plugins-or-destinations-from-greenshot/
|
||||
tags: []
|
||||
---
|
||||
|
||||
This document describes how to make Greenshot skip loading of certain plugins, or not to show certain destinations.
|
||||
|
||||
Plug-in
|
||||
-------
|
||||
|
||||
The best way to remove plugins, is to use the installer and only select those you want.
|
||||
But sometimes this is not possible, so we build a way into Greenshot to skip the loading of them.
|
||||
|
||||
This can be done by added a setting to the "Core" section called "ExcludePlugins" to excluding plugins, or you can use "IncludePlugins" which has a list of every plugin you want and the rest is automatically excluded.
|
||||
This might solve the adding of additional plugins when new releases bring new plugins, but you might also loose functionality without knowing: in the next release the editor is a plugin.
|
||||
|
||||
Here is an example on how to exclude plugins by adding the plugins you don't want to the greenshot.ini:
|
||||
|
||||
1. Find the greenshot.ini by reading [this](http://getgreenshot.org/faq/where-does-greenshot-store-its-configuration-settings/) or modify/create the greenshot-fixed.ini as described [here](/faq/how-can-i-control-greenshots-configuration/)
|
||||
2. Stop Greenshot
|
||||
3. Open file in an editor
|
||||
4. Modify the line which should be under the "[Core]" section of the ini starting with "ExcludePlugins" (or add it, if not available), you can add all the plugin names with a comma in between.
|
||||
5. Save the file
|
||||
6. Start Greenshot again.
|
||||
|
||||
An example to exclude the box and dropbox plug-ins add the following line somewhere under the ```[Core]``` section:
|
||||
|
||||
```
|
||||
ExcludePlugins=Box Plugin,Dropbox Plugin
|
||||
```
|
||||
|
||||
The names of the plugin are visible in the Plugins tab of the settings or the greenshot.log (due to unfortunate decision while coding, they all end with " Plugin".
|
||||
|
||||
For completeness we describe the plugins here (do not include the quotes!):
|
||||
|
||||
* "Box Plugin"
|
||||
* "Confluence Plugin"
|
||||
* "DropBox Plugin"
|
||||
* "ExternalCommand Plugin"
|
||||
* "Flickr Plugin"
|
||||
* "Imgur Plugin"
|
||||
* "Jira Plugin"
|
||||
* "OCR Plugin"
|
||||
* "Office Plugin"
|
||||
* "Photobucket Plugin"
|
||||
* "Picasa-Web Plugin"
|
||||
|
||||
|
||||
Destination
|
||||
-----------
|
||||
|
||||
If you want to exclude destinations only, for example the office plugin has multiple and you might want only one of them, you can modify the "ExcludeDestinations" line.
|
||||
|
||||
The names of the destinations are a bit harder to find, here is the currently known list (do not include the quotes!):
|
||||
|
||||
* "Box"
|
||||
* "Clipboard"
|
||||
* "Confluence"
|
||||
* "Dropbox"
|
||||
* "EMail"
|
||||
* "Editor"
|
||||
* "Excel"
|
||||
* "External MS Paint"
|
||||
* "External Paint.NET"
|
||||
* "FileDialog"
|
||||
* "FileNoDialog"
|
||||
* "Flickr"
|
||||
* "Imgur"
|
||||
* "Jira"
|
||||
* "OCR"
|
||||
* "OneNote"
|
||||
* "Outlook"
|
||||
* "Photobucket"
|
||||
* "Picasa"
|
||||
* "Powerpoint"
|
||||
* "Printer"
|
||||
* "Word"
|
||||
|
||||
**See also:**
|
||||
|
||||
[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/)
|
||||
Loading…
Add table
Add a link
Reference in a new issue