#982 Application Forgets Collapsed View of Groups in Some Cases

open
nobody
None
5
2014-08-22
2011-07-30
Gil
No

I created a test data base with a single group and a single entry in it. Initially, the view of the group is expanded.

If I collapse the view of the group and then maximize the window, the view of the group is expanded again.

If, while the window is maximized, I collapse the view of the group and then restore the window, the view of the group is expanded again.

If I collapse the view of the group, then minimize the window, and then restore the window, the view of the group is expanded again.

If I collapse the view of the group, then lock the workstation (database is configured to lock on workstation lock), then unlock the workstation, then give the passphrase to re-open the application, the view of the group is expanded again.

Discussion

  • Gil
    Gil
    2011-07-30

    I am running 3.26.01 (4352+).

     
  • DrK
    DrK
    2011-08-14

    I can reproduce this as you describe but I can't seem to determine why it happens!

    In your test case, if on opening the database, the group is collapsed and your maximize, it doesn't get expended but once it's entry has been selected, it does. Also, if you add another entry in another group and collapse all, when you save the database, the last group gets expanded and its entry selected!

    If you expand your test database to include more groups (at least one entry in each), then it is only the last group that is expanded and its entry selected. Also, if there is at least one entry in the root directory (below all the groups), then this problem doesn't occur.

    David

     
  • Gil
    Gil
    2011-08-14

    I first noticed this problem with a real database. That database does have entries that are not in any group. That is, the problem does occur with a database that includes entries outside any group.

    Further testing now shows that, in some cases, the application forgets which entry is selected when maximizing/restoring the window.

    For example, consider a test database with "root entry" X, one group Y, and one entry Z in that group. Suppose that, initially, group Y is expanded, entry Z is selected, and the window is not maximized. Then:
    1. Maximize window.
    2. Restore window.
    3. Select group Y (but don't expand/collapse).
    4. Maximize window.

    At this point, entry Z is selected again instead of group Y.

    If step #3 is changed to "collapse group Y" (leaving it selected), step #4 causes the same result (Y is expanded with Z selected).

    All this occurs despite the existence of X, outside any group.

    I do agree that the problem may be circumvented if certain operations intervene between steps #3 and #4 (e.g., Browse to URL, Run Command).

     

  • Anonymous
    2011-10-27

    Every time that version 3.26 (on XP Pro SP3) is minimized and then restored from my system tray, I find that the tree is re-expanded, despite my having completely collapsed it before minimizing the app. I don't want any of my entries to be seen, and this automatic revelation to any passer by, every time I have to restore the app, is now a built-in compromise of the very security for which the app is supposed to exist.

     
  • Gil
    Gil
    2012-01-27

    I still have this problem with 3.27. Is there anything that I can do to help with debug?

     
  • DrK
    DrK
    2012-01-27

    I understood that I fixed this for you in the version I uploaded to the web site on 15 November (pwsafe_3377061E.zip) and I said that this would be in the next release.

    V3.27 was released in October before this fix was confirmed by you.

    V3.28 is due to be released sometime in February.

    David

     
  • DrK
    DrK
    2012-01-27

    Sorry - just noticed that this has an ID of 3382901 and the fix was for 3377061.

    However, this issue is unlikely to be investigated or fixed before 3.28.

    David