DonationCoder.com Forum
DonationCoder.com Software => Mouser's Zone => Screenshot Captor => Topic started by: johnfdeluca on August 19, 2011, 09:22 AM
-
Let me start by saying that I love this tool....it's wy I joined Donation Coder several years ago and I use SC just about every day. I am expereincing a new issue that I hadn't seen before and a search on this forum reveals no hits. I often use the arrow tool to point someting out in a screenshot and when I start typing endpoint text, it is very slow to 'paint' the text into the screenshot.....taking several seconds per character. Any ideas?
Windows XP SP3
Screenshot Captor v2.95.02 by DonationCoder
My workaround is to type the text in another app, then copy/paste into the endpoint text field in SC.
-
i've noticed this once before too..
it may have to do with antialiasing kicking in with screenshot magnification not at 100%.
can you check this option and see if it helps:
[ You are not allowed to view attachments ]
oh and also (more importantly):
[ You are not allowed to view attachments ]
-
I checked both options and they are the same as your screenshots but it is still very slow. I should clarify that it's not just slow to paint....but also slow to even show the typed characters in the endpoint text entry field in the options. If you can think of anything else that might address this, let me know....I've uninstalled and reinstalled SC to see if that did the trick and it did not.
-
does it happen on every screenshot when you try to add an arrow, or only one?
does it happen even if magnification is at 100%?
if you drag the arrow around is that super slow also?
-
Every screenshot at all mag levels, including 100%.
-
very odd.. it definitely shouldn't be so slow, so it's a bug somewhere.. but where.
i still suspect the antialiasing routines. can you tell if antialiasing is disabled when you are typing text? the way to check is to compare the look when you are typing text for the arrow against what the screenshot looks like after you disable object editing mode (by clicking the button with the O and arrow).
-
The text doesn't appear to undergo any difference visually wile typing vs. clicking o+arrow.
Attacments of objects and ini.
-
ok first result is -- with my screenshto captor settings and your screenshot+object i can edit that arrow text very rapidly.
so.. now to figure out what is it about your settings or setup that makes it slow..
i will try your screenshot captor ini file now..
even with your screenshotcaptor.ini file the text edits very quickly.
i'm going to email you my current screenshotcaptor.exe file just so we can make sure there isnt something up with that.
-
I just want to chime in and say that I've experienced this as well. But that was on my old slow computer so I thought it was a symptom of my PC being really bad.
I just got SC reinstalled on this new PC and haven't used the arrow text yet so I'm not sure if it will happen to me again.
-
i used to have this problem but mouser fixed it through one of the updates, can't remember which one. i suggest deleting/renaming the ini file and make sure to have the latest version. also the number of images in the screenshot folder might have an impact, though i'm not sure.
-
John,
I just managed to reproduce this. It's definitely a bug, and it's definitely related to SC trying to anti-alias the text while you are editing it -- even when you tell it not to. Seems that for some random reason sometimes high-quality anti-aliasing is being enabled during editing.
Working on a fix now.
-
Awesome....glad you were able to replicate the issue. Looking forward to a fix!
-
Can you try this version:
https://www.donationcoder.com/Software/Mouser/screenshotcaptor/downloads/beta/ScreenshotCaptorSetup.exe
Hopefully it will not only fix the slowdown bug but also speed up editing of the text from what it was before and improve the look of anti-aliased text (especially in memo boxes) when you use the default settings to anti-alias when not editing.
Let me know!
-
Much faster with endpoint text tho still a minor lag for me (checked my settings to ensure they were right based on your previous feedback). Vast improvement though, thanks!
-
I see something else that could still be slowing it down.. Ill upload another beta soon.
-
Can you try the new beta (same url: https://www.donationcoder.com/Software/Mouser/screenshotcaptor/downloads/beta/ScreenshotCaptorSetup.exe) and tell me if this performs a little better with regard to arrow text editing speed.
Note: this version also changes the connection points for labeled arrows, as well as memo box transparency method.
-
Well.. how's the new version?
-
tap.. tap... is this thing on?
-
Sorry.....I was on vacation. Will download, test and provide feedback once I get a few free mins.
-
Just tried it (new version above) and it is very slow again.....like really slow. Checked options and they are set properly per your previous suggested values.
-
crap >:( :down:
I just don't understand it :(
Is there any way you could make a screencast showing you selecting an image with arrow text, then editing the arrow text and showing the slowness?
The main thing i really need to see is if the font is trying to anti-alias while you are typing.
I may have to upload a test version too that can output some debug information for me to check on.
I just wish i understood what was going on.
Anyone else experiencing slow arrow text editing with the new beta version?
-
And maybe attach again an image which exhibits the slow editing behavior with the new version?
Perhaps i can replicate it again..
-
Does it help if on the Drawing Object Options tab you select "Anti-alias Object Display: Never" ?
-
Question -- do you have the shadow checkbox checked? if you uncheck it (on all arrows on the screenshot) does it solve the problem?
-
I just encountered the slow arrow text just now, randomly, right after making v2.99 live and after a week of trying everything i could to trigger it.
So clearly the bug is still lurking about -- and i'm back on the hunt for it.
Note that it's definitely (my occurrences of it at least) a very random thing -- going in and out of object mode or doing various things makes the problem completely go away).