Settings and activity
8 results found
-
25 votes
Jean-Luc Duprat
supported this idea
·
-
1 voteJean-Luc Duprat
shared this idea
·
-
24 votesJean-Luc Duprat
supported this idea
·
-
1 vote
An error occurred while saving the comment An error occurred while saving the comment Jean-Luc Duprat
commented
The stack trace was automatically capture by a tool we use at Apple. I was just resizing the window, the app had most likely been running for several days/weeks by that time. I'll double check if there's anything in the logs...
Jean-Luc Duprat
shared this idea
·
-
28 votesJean-Luc Duprat
supported this idea
·
-
25 votes
The correct tab will be remembered when you restart the app on the next version. The safes themselves can be remembered by following these instructions:
1) Issue the following command on the terminal
defaults write com.app77.pwsafemac NSQuitAlwaysKeepsWindows -int 12) Open all the safes you want
3) When quitting the app, instead of closing its windows or pressing CMD+W, simply press CMD+Q or choose pwSafe→Quit pwSafe menus.
Jean-Luc Duprat
supported this idea
·
An error occurred while saving the comment Jean-Luc Duprat
commented
In particular, the proper tab (iCloud | Mac) in the first screen containing the file should also be selected.
-
3 votes
This is a known bug which will be fixed on the next update. Thanks for telling us about it.
An error occurred while saving the comment Jean-Luc Duprat
commented
To clarify, when a generated password contains an underscore, it looks visually like a space.
Jean-Luc Duprat
supported this idea
·
-
34 votes
That procedure might help:
1) Issue the following command on the terminal
defaults write com.app77.pwsafemac NSQuitAlwaysKeepsWindows -int 12) Open all the safes you want
3) When quitting the app, instead of closing its windows or pressing CMD+W, simply press CMD+Q or choose pwSafe→Quit pwSafe menus.
Jean-Luc Duprat
supported this idea
·
Here is what was logged about this event:
5/23/13 7:48:25.908 PM pwSafe[37906]: An instance 0x7ff7e289da80 of class SafeFile was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x7ff7e703c150> (
<NSKeyValueObservance 0x7ff7e7091140: Observer: 0x7ff7e701e000, Key path: namedPwPoliciesNames, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x7ff7e70437e0>
<NSKeyValueObservance 0x7ff7e70345b0: Observer: 0x7ff7e703c040, Key path: namedPwPoliciesNames, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x7ff7e70437e0>
)