QSA tip wording

tullik

QSA tip wording v.1.8.0.468

The tip wording needs a slight change (like in the Health mouse overs) so it doesn't say 100 out of 100 can be improved.

08-22-2008_04-38-30.jpg

jv16

You are correct, this problem is now fixed, thank you for reporting! The fix in question will be available in the next released version of PowerTools.

mikebcda

Very slightly off-topic, but still relating to wording in the QSA -- I've got a "ticket" in on this one as of a week or 10 days ago, but still haven't seen anything back other than the auto-receipt acknowledgment.

When running the QSA, it finished with the message (this is from my memory, not necessarily verbatim) "1 error found - fix?", with no other detail or explanation. I gambled and ticked yes, and so far haven't seen any resultant problems. But obviously I'd like to know what the supposed problem was before taking any action.

tullik

MikeBCda wrote
... But obviously I'd like to know what the supposed problem was before taking any action.

I have never experienced such a dialog during QSA. My curiosity is also aroused.

Use the backup tool to see what (if anything) was backed up at the time you clicked "yes."

If there is a registry and/or file backup, describe it here -- it may provide a clue about what the program "thought" needed to be fixed.

mikebcda

No backups found -- and while I wouldn't swear to it, I don't remember being asked if I wanted a backup, as is normal with the other tools (I'm set for "always ask").

There were about three version-upgrades over a fairly short period (a month or so) this summer or fall, and this occurred with the first of them, sorry I don't remember the specific build but that would show on the ticket. I've since updated with the others, but haven't tried the QSA again since then.

tullik

If it happens again, reply "no." Then force a QSA from the main window File menu.

If the message repeats, restart PT in Debug mode and force a QSA again. If you still get the message, close PT immediately and post the debug logs here for jv16.