screen refresh problem when adding groups
Popular easy-to-use and secure password manager
Brought to you by:
ronys
Very easy to reproduce:
1. Create new password safe.
2. Right-click and select Add Group.
3. Add an (empty) group called 'group one'.
4. Right click again, add group called 'group two'.
5. Repeat with 'group three'.
At this point, two group threes appear.
The situation gets more worse as more groups are added (left as an exercise for the reader)
Are you on windows?
Are you using a windows version earlier than v3.38.01?
I have seen this problem before on windows, but not anymore using v3.38.1
Also, when you see this problem, press F5 or View>Refresh and see if it clears up.
IIRC, in versions prior to V3.38.1, F5 cleared up the problem.
I believe that I fixed this for 3.38.1.
Personally, I would put up with this minor issue in 3.37.1 and earlier releases until the problem with DB entry corruption in 3.38 & 3.38.1 has been fixed.
Hi guys,
Yes, I am on Windows.
The problem occurs on 3.38.01 as well as previous versions.
Pressing F5 clears the problem (it's only the screen that is drawn wrong -- that's why I put 'screen refresh problem' in the title).
It looks like it's something to do with sorting the entries before drawing.
Yes, it's minor, that's why I put priority 9 (assuming 1 means highest priority!)
Thanks
I can't reproduce this in 3.38.2
I was able to reproduce this in v3.38.2 after trying multiple times.
It doesn't always occur.
Try the OP experiment multiple times and you might see it. It also seems like a left click instead of hitting Return when after naming the group makes a difference. Trying the OP experiment multiple times, it seems like when I use Return after naming the group I didn't see the issue as often.
I believe the below steps might more consistently show the issue:
At step 6 is where I see the empty group 'g2' and entry 'e2' having the same name of 'e2' in the tree. Sometimes it's 'e2' and 'g1' that will have the same name of 'e2'. F5 (Refresh) clears it up.
I'm sorry but, if it only occasionally occurs, it makes it much harder to find and, since a workaround exists (Refresh – F5) and it doesn’t affect data integrity then IMHO it is very low priority.
I agree that this is not high priority.
I would rather see some of the more repeatable UX/UI issues addressed first (e.g. see bugs #1313 - 1318).