Ah! I see what's been happening now.
I've been using QuicKeys 4.0.7 to intercept all of my Command-Q and first put up an "Are you sure you really want to quit?" dialog. Then QuicKeys selects the menu 2 item containing "Quit." I guess when QuicKeys does it, QRecall somehow sees a Shift-Option or something, and does the uninstall. (In Activity Monitor, I can see the QRecallMonitor & QRecallScheduler processes disappear, so that must be what you mean by "uninstall," or at least the consequence of an uninstall ? perhaps your uninstall is removing a launchd job.)

In any event, if I personally do the Quit explicitly from the QRecall menu, then the quit is fast, and Preauthorization sticks. So I made a QRecall-specific QuicKey to do a Command-Q keystroke instead of a menu selection for me, and all is well with QuicKeys now, Preauthorization-wise (and the two aforementioned processes remain).

Whew! I don't understand the interaction between the QuicKeys menu selection & QRecall, but my workaround solves the proximate problem. (Yay!)

Woops, in my report, when I was talking about the off-topic curiosity of my slow quits, I said that the File menu was black for the duration. Of course, I meant the QRecall menu.

Thanks, James. Done; check for my report.

Every time I launch Qrecall 1.2.3.8, from the very first time I ever used it, it asks me to authorize with my Mac password, even though I've previously pre-authorized in prefs.



How can I make it stick? Can't it get stored in Keychain or something?

OS X 10.6.8