Or an added line in history flagging which entries have conflicts. Or a new field in History flagging which entries have conflicts. Or a new flag next to entries in History showing which entries have conflicts. Any of these would need some flag on the main tab to show you need to go an look at the merged conflicts or they will solve nothing for 90% of users.
If that method is structurally complicated would it be possible to just append a line at the top of the Notes field to say "Conflict YYYY-MM-DD merged to history"? Then, even if there were more than one conflict, when they have the time and headspace to deal with it, the user can go and compare which history instances correlate with the dates appended to the top of the notes field. The already existing conflicts are then visible without need to dig for information or delay sync as this is often a...
This is a simple way to flag which entries I would then know to have a quick look in their History and manually merge the changes, before the history is buried or eventually deleted. It could be done at any time if the flag just remains somewhere visible on the entry - rather than having to make a list to cross-reference. Excellent, elegant solution in the short-term to see where KeePass had to bump some changes into the recesses of History. I do hope this is easy to implement as it would satisfy...
I have now found out that Samsung have moved the keyboard switching button from the right to the left side of the navigation bar, thus hiding it behind the voice input button... oh actually you can long tap the keyboard or voice input button to toggle between them.
Hi. Using KeePass on Android, I have not yet done the ADB thing to allow the Keyboard Swap function to work on this new phone. While looking in settings I ticked to activate Keyboard Swap but as the function was not activated by ADB it couldn't use it so it kept flipping from the screen where I'd enter my master password to test configuration to the page detailing how to use ADB to activate the Keyboard Swap function, with no way to get out of the loop. In Android Settings I changed the default keyboard...
Thanks Paul. I have only ever populated the auto-type Target window field by using the dropdown which is auto-filled by KeePass for the various open windows - assuming a simplistic manual entry could lead to a misattributed one. (Annoyingly these days Zoom's ZPToolbarParentWnd is always at the top when it used to be the last one being used). I see I can type into that box but I assumed the text needs to be specific and that what I see might be a friendly text name for the actual technical ID being...
Thanks Paul. I have only ever populated the auto-type Target window field by using the dropdown which is auto-filled by KeePass for the various open windows - assuming a simplistic manual entry could lead to a misattributed one. (Annoyingly these days Zoom's ZPToolbarParentWnd is always at the top when it used to be the last one being used). I see I can type into that box but I assumed the text needs to be specific and that what I see might be a friendly text name for the actual technical ID being...
Sorry - this should be for KeePass 2 - since restarting Firefox SourceForge kept the text I had started writing but must have reset the dropdowns.