![]() ![]() Typinator is not the only program affected by this secure mode. Not only do I get their name spelled right every time, I seriously challenge you to write the whole tribe's name out - say 3-4 times in getting an article out on deadline. I had a simple abbreviation (t-o) that Typinator expanded to Tohono O'odham. As you can tell I'm seriously POed by this. I hate the Johnathon Ive "The user is stupid" mode forced on OS X that has now cascaded down to 3rd party developers. Second, not only does the user not know what happened, I can find absolutely no way to turn it off or at least modify its use. First, you made a fundamental change and in NO WAY NOTIFIED YOUR CUSTOMER. I powerfully object to the way you've handled this on two counts. ![]() You'll have to read the email with the subject line HEY! HEY! What the 8888!! for details. ![]() This bit me hard for the first time after the most recent update. ![]() There are in fact several ways this can be done. The current Mac OS system does allow "secure keyboard mode" but it mandates that the program release said "secure" when it is not in use. Normally I moderate my concerns, but I was so angry about this that I fired both barrels. I'm a bit late to this discussion, but I just sent agilebits support a "burn before send." email. Not trying to berate you, just offering another user's viewpoint on a question that you are actively researching. Honestly, if I had a reasonable way to completely disable Secure Input mode on my system, I probably would, because I have yet to notice a situation where it was activated under circumstances that would actually put private information at risk (with the exception of bullet-masked password fields), but have encountered numerous situations where it slowed me down by interfering with an otherwise simple task because it blocked Typinator. If it was there, it wasn't made clear what it did, because I would have waited to upgrade had I known that this would prevent me from using Typinator shortcuts within 1P. What bugs me here, though, isn't that you've activated this security feature-it's that it is a change from 1P5 that I don't recall seeing in the change log presented to me by the updater. Or Secure Input could be deactivated specifically for fields that are hold data not normally kept secure from one's own system, such as name or email address. Under normal circumstances, for example, Secure Input mode might be turned on in some apps only when a field is set to display bullets instead of characters-1P could do the same, turning it on only for fields that would be hidden when "Conceal Passwords" is active. So if this option were available, I'd turn it off for software licenses only.Īlternatively, instead of turning it off by item types, you might allow it to be disabled for non-secure fields, or just specific fields, regardless of item type. I previously kept license codes in a spreadsheet, which doesn't really hide anything from keyloggers. The only reason I store license codes in 1P is because I can-I bought 1P for passwords. What if Secure Input mode could be optionally disabled by item type? For example, I personally feel little value in hiding the information added under a software license from keyloggers. I know I can enter one license and then duplicate that entry, and change just the parts that are different (normally just name, version, and license code), but even that first one can be a hassle, as my email address gets annoying to type all the time. Typinator saves me having to retype name and email with these. I frequently acquire bundles of software, with several licenses being added at a time. I also use Typinator extensively, and with 1P6, the big hassle for me comes with Software Licenses. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |