Posted 28 October 2011 - 05:59 PM
I got the 2.6 update. You'll see (I assume) that I submitted a crash report. It occurred hitting the skip button for captcha. Now I'm also getting similar behavior to what I described above with the exception that when I entered the captcha and hit Go, instead of the spinning wheel and nothing, instead I got the spinning wheel then it disappeared as if it were submitted however then doing the "Bring to Front" I get the same captcha popup i.e. same code except now the Go button is greyed out and the only option is Skip. If I click Skip I'm back to the same place. Same captcha with only a skip option.
Even if this were working perfectly, there is a real lack of elegance and intuitive and useful UI/UE in the process. First of all, having to wait for the user to click one or the other for a captcha is nonsensical. If you are checking multiple keywords on multiple search engines you are looking at hours of process. Most of this should run in the background. Then if there is something requiring a captcha, put that into a queue for the user to deal with when they are ready and let the non-captcha items run in the meanwhile.
I see you are discouraging users from doing multiple search engines and there is no Select All option - but why? That means more work for the user I don't want to go clicking through a bunch of stuff for every site. If there are limitations to the software then design a methodology that works around those limitations but make it as simple and useful as possible for the end user. I was pretty stoked to try out this software that I laid down a good chunk of change for - SEIntelligence, SERank, Sitemap automator. I'm pretty disappointed right now.