Now two pretty giant things should jump out when you compare the two. (which should have zero bearing on a simple scroll capture), on Windows 7 圆4: 0 - with various userscripts/octotree/etc. On both, the exact same client area (inner Chrome Window auto-selected with outline) of THIS Github issue window as I type, taken in Chrome DEV 圆4 Version. PNG output, no cursor, all DEFAULTS for ShareX scrolling (paging/etc.).
:(Īll settings the same (as they appear to translate).
I agree with most that ShareX beats all, but have to disagree with the statement that nothing beats ShareX specifically on scrolling captures. I was about to open a new issue myself but since beat me to it, I wanted to simply post a side by side of a capture I just took with today's DEV build vs a decade-old version (v10.0.2) of Techsmith Snagit (commercial). With that said, scrolling capture is IMO it's absolute number-1 weakest feature and unfortunately has been for a long time.
We peasants really appreciate you guys 💖įirst I'll start by saying that I love ShareX's. I've tried tons of softwares for scrolling screenshots and haven't found anything that does the job as well as ShareX (even commercial ones don't come close). This will save lots of time, especially when you have to take multiple screenshots.įinally, thank you to all the contributors for your hard work 🙏. The auto feature makes a good guess most of the time but when it doesn't and the users already know the values won't change, it's more efficient to input once and save them for all subsequent captures. Fixed values for trimming edges and combining adjustmentsĬurrently for scrolling capture, users can check " Guess offsets and combine images" to have ShareX automatically insert values for trimming edges and combining adjustments (or leave it unchecked and the values will be 0) in the " Output" tab I think it'd be nice to be able to manually choose where/when to end the taskĢ. And when it's the end of the scrolling window, ShareX would capture duplicates of the final shot to fill the maximum count (in this example, 15). ShareX would sometimes arbitrarily capture fewer than that (11,12,14.), even though there's still content below. A way to manually signal when to end capturing:Ĭurrently with v14.2.1, users can choose a maximum scroll count (Let's say 15). Hi, I'd like to humbly suggest two small improvements to ShareX's scrolling capture:ġ.
0 kommentar(er)
