#175 Resetting Double Click Default Action


I have a wierd problem. I have password safe installed on two Dell computers (one a desktop and the other a laptop) for which I am the administrator. Both are running XP.

I change the default action of double click from 'browse to url' to 'autotype'. It works just fine on the desktop but as soon as I end password safe and re-launch it on the laptop, it goes back to 'browse to url'.

I get no error messages or any indication whatsoever that the change didn't get saved.

Thank you.


  • DrK

    DrK - 2009-10-20

    The reason is that the default value is not a database preference (stored in the database) but an application preference (stored in the pwsafe.cfg file). You would have to set your required value on each computer/user that you use.

    Obviously, the new value per entry is stored with the entry in the database. A possible solution is to add a database default preference. The question is then how to deal with it and the current much older 'application' preference? Migration is not trivial.

    I am afraid that it is working as designed but this design is not optimal and not trivial to change. Had we known years ago that we would implement a value per entry, then we would have made the default a database preference. Hindsight is always 20-20.

    Just set the default to be what you want on each computer/user you use and it will work as you want. I will close this Support Request - you can always re-open if this does not solve your problem.


  • nhm1010

    nhm1010 - 2009-10-22

    I guess I didn't make my self clear. I performed the same action on both computers. It worked on the desk top but failed on the laptop. I just remembered something. This laptop seems to have problems saving any settings. I tried changing the size of the window and that setting wouldn't stick either. I had to go into the cfg file and manually change it.

    Why does this system refuse to save my changes?

  • DrK

    DrK - 2009-10-22

    The only reason why PWS would not update the configuration file is if it believes that it is a read-only file or that you do not have write access to it.

    Since you can write to it using an editor (I assume that you are using the same ID on the computer with the same access rights), it can't be that. I also assume that you don't have the configuration file open in an editor or other program at the same time as starting PWS that might cause a sharing violation.

    We will look at that code again but I don't believe it is in error - subject to change without notice :-)

    Lastly, the debug version does show the read/write status of the configuration file (or if the user is still using the Windows registry) in the status bar to aid testing. We don't do this in the normal release version as it just adds clutter. If I can't find anything, I might ask you to test a debug version just to see what it thinks about the configuration file on both of your computers.


  • DrK

    DrK - 2010-01-06

    Closed as no further input from the user in over 2 months.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks