Menu

#2110 Open a new window

KeePass
closed
nobody
None
5
2016-03-25
2016-03-23
zeromido
No

Hi,
Please add open a new window option
I actually requested that because I needed to open the same database in a new tab (or window)
and please don't forget about review changes made to the database before saving.
Regards

Discussion

  • Paul

    Paul - 2016-03-24

    The way to open the same database twice is to turn off "single instance" under Tools > Options and then open a scond copy of KeePass.

    cheers, Paul

     
    • zeromido

      zeromido - 2016-03-24

      This causes a plugin (KeePassHttp) to fail
      I meant to add a sub menu in "File" menu containing new database and new window

       

      Last edit: zeromido 2016-03-24
  • Dominik Reichl

    Dominik Reichl - 2016-03-24
    • status: open --> closed
     
    • zeromido

      zeromido - 2016-03-24

      I meant to add a sub menu in "File" menu containing new database and new window
      Also, please don't forgrt about review changes before saving and reset configuration.
      Cheers

       
  • Paul

    Paul - 2016-03-25

    KeePass doesn't and shouldn't open the same database in separate tabs as this is asking for mistakes to be made IMO.

    cheers, Paul

     
  • Dominik Reichl

    Dominik Reichl - 2016-03-25

    Opening a database twice (as tabs or windows) will cause them to go out of sync (and when saving, KeePass will ask whether you want to synchronize or overwrite the file on disk). I cannot imagine any scenario where such an asynchrony could be useful/intended.

    If you really want this for some reason, run two KeePass instances like Paul described. Plugins might need to be enhanced to support this.

    Best regards,
    Dominik

     
  • T. Bug Reporter

    T. Bug Reporter - 2016-03-25

    The only scenario I can envision where this might be useful is if you made changes to the database, forgot what they were, and now want to compare the copy in memory with the original in order to decide whether to commit those changes. (If I'm wrong, please explain your own reasons for wanting two instances if the same database open at the same time.)

    If I'm right about why you want this, the easier thing to do would be to save the changes, add a "Last Modification Time" column to the main view temporarily, sort by that column, review the most recent modifications, and use the History to restore the old versions of the records unintentionally changed.

     

Log in to post a comment.

MongoDB Logo MongoDB