BUG-1919: Screenshot works once on Internet Explorer.PR #157 - Fixing textbox issue with polish letter "ą".
GREENSHOT IMGUR ERROR UPDATE
GREENSHOT IMGUR ERROR FULL
Bug #149: If using a full screen capture of the current monitor, not the default, the mouse cursor is not visible.Bug #124, some minor issues with the EmailDestination.BUG-2542: Fix for shutdown issue (ImgurPlugin).BUG-2544: Enabled TLS1.1 & 1.2 to fix jira connectivity and do not use the JIRA session support as this was deprecated.BUG-2535: Greenshot selects invisible windows fix was suggested by Raymond Chen here:.BUG-2644: Fixed a NPRE when exporting to Powerpoint when it's not running yet.
GREENSHOT IMGUR ERROR 32 BIT
BUG-2693: This should fix an issue where Greenshot doesn't detect a MAPI client, we weren't looking at the 32 bit location.
It might also work on Windows 8, but we don't have enough hardware to test. This is only tested on Windows 7 and Windows 10, and as always comes "as-is" with no guarantee whatsoever. We've also added some new Windows 10 functions, like OCR and sharing with Windows 10 apps. NET 4.7.2 which solves some general issues in the area of Internet Explorer capturing, TLS communication and some other minor issues. We need to track the issue with our ticket system, and not in here, for one we don't want to use SF (as they pretty much turned the back to us) and for us it saves time.This is the first Greenshot which targets. Maybe Imgur is blocking again, whatever reason, maybe there is a authorisation issue and the token is not updates. I will need the log, so I can see what is happening. You can find the location of the log via the information here: (If SF doesn't have issues, this should work) please report a bug and upload your greenshot.log here: So we sometimes are with our backs against the wall!Īnyway, back to the issue at hand. We don't get any feedback on this, it might be that we are hitting a limit and our (multiple times) requested whitelisting might be inactive (or not working). On top of that, Imgur might throttle (or even break) the uploads for a user OR an application. I can imagine you are somewhat annoyed, we are trying to rebuild Greenshot so it's going to be easier to quickly respond to such issues, this unfortunately is one of the complex things we are working on: Greenshot 2.x and our Website relocation as SF has problems hosting our website!! To put it in perspective, if Greenshot would be paid application with (paid) support I would have money to make someone do my laundry/garden/cleaning etc and I had time to phone/email/orwhatever Imgur to ask them why a certain user can't upload. If the issue occured, like last with the recent change, during one of our more complex tasks we have been working on, than it takes longer as Imgur isn't our main focus. As Greenshot is developed in our spare time, it's not always possible to react in hours or days so sometimes we need more than weeks. Than we need to act accordingly, and make a change, which sometimes is more complex. We can't smell that there are issues, without people actually reporting them. Imgur has changed their API a couple of times, which prevented us uploading to it. You need to consider that we use a service we do not control, which is Imgur.
Without having more information, it would be hard to say what is the problem.
0 kommentar(er)
