Issues
- Support environment variables in configFEATURE-1169
- Auto save in EditorFEATURE-1138
- Detect Window in rdp/vnc sessionFEATURE-1014
- Create a new .greenshot file format, preferably portable over versions and platformsFEATURE-1007
- large crosshair for the 1. clickpoint of captureFEATURE-999
- Opening last capture in explorer should select/jump to the fileFEATURE-998Resolved issue: FEATURE-998Robin Krom
- Enable a frame for screenshotsFEATURE-997
- configurable shortcut keys (at least copy to clipboard)FEATURE-993
- When reusing the editor, it is not brought to the frontFEATURE-992Resolved issue: FEATURE-992
- Font is very tiny on high dpi displaysFEATURE-989
- Command line to open an image with editorFEATURE-988
- Update without user interventionFEATURE-984
- Add counter for ABCFEATURE-979
- Finetune magnify functionFEATURE-978
- Open Prefered Output Folder via Open Menu and ButtonFEATURE-976
- Easier object selection when in edit modeFEATURE-975
- When capturing small areas it is not possible to see the size of the captured areaFEATURE-971
- Add zoom and unzoom to manage larger imagesFEATURE-969Resolved issue: FEATURE-969
- Add Preview function to Torn EdgeFEATURE-961
- Capture full screen without taskbarFEATURE-956
- Add common picture objectsFEATURE-952Resolved issue: FEATURE-952
- Use Inno-Setup 5.5.9 for improved securityFEATURE-949Resolved issue: FEATURE-949
- Ability to enhance Contrast of screenshot in Image EditorFEATURE-948
- Open Captures in Single Editor WindowFEATURE-942
- capturebeyond screen sizeFEATURE-939
- [Storage Location] Define directory patternFEATURE-912Robin Krom
- Keyboard shortcut for delayed captureFEATURE-905
Support environment variables in config
Description
Environment
Activity
Stefan HelmsJuly 4, 2019 at 3:08 PMEdited
I strongly support this feature request and believe this could easily be solved by applying the same templating used for OutputFileFilenamePattern to those other two Fields/Parameters (or consequently all paths in configuration…).
We are already deploying Greenshot, but need to change the configuration due to pending infrastructure changes. We need to preconfigure OutputFilePath to something like “C:\Users\${user}\Work Folders\Pictures\Screenshots” in either greenshot-default.ini or even greenshot-fixed.ini.
This is a tiny but very inconvenient weakness in an otherwise outstanding product, so I really hope you can make this change happen. Please reconsider your priority rating for this feature because it’s a huge PITA for administrators in large environments and likely very easy to solve.
Other places this has (implicitly) been asked for:
https://greenshot.atlassian.net/browse/BUG-2321
https://superuser.com/questions/1301670/greenshot-storage-location#comment1942833_1301670
Thank you very much for all the great work you’re doing!
I would like to see support for environment variable support in the greenshot.ini like in the following to lines:
OutputFilePath=C:\Users%UserName%\Pictures
OutputFileAsFullpath=C:\Users%UserName%\Pictures\dummy.png
This would it make more easy using greenshot in a portable way.
Above used output path should be good for every user who started with the default ini file in the program folder.
Thanks in advance