Menu

#103 FR#2038 coded

KeePass_2.x
closed
nobody
None
5
2016-04-13
2016-04-11
No

Hello!

I have just finished implementing Feature Request #2038.
I don't know the appropriate way to add the new code, because the repository is private.
Can you help me please?

Thanks,
Peter

Discussion

  • T. Bug Reporter

    T. Bug Reporter - 2016-04-11

    Probably the best way would be to post your code here (in a ZIP file, for example). Dominik will take care of incorporating it into the program - or else he'll contact you if he has questions or problems with your work.

     
  • Peter Paluska

    Peter Paluska - 2016-04-11
     
  • Paul

    Paul - 2016-04-12

    You can attach files directly to posts using the "add attachments" button at the bottom, or if the code isn't huge you can post it direct with code highlighting.

    cheers, Paul

     
  • Peter Paluska

    Peter Paluska - 2016-04-13

    The modified files:

     
  • Dominik Reichl

    Dominik Reichl - 2016-04-13
    • status: open --> closed
     
  • Dominik Reichl

    Dominik Reichl - 2016-04-13

    I found the following problems:

    • Tooltips are not displayed at the correct location, which causes various problems like interrupting hovering (when moving the mouse cursor from top to bottom over a group that has a tooltip, the tooltip hides the following groups and does not go away when moving down).
    • Sometimes the tooltip flickers or is not displayed at all (especially when moving onto a group from right to left).
    • Sometimes the tooltip starts to display when moving away from a group (i.e. too late).

    With a custom tooltip, it probably is not easy to replicate the standard Windows behavior. Thus it may be better to get the child tooltip that the tree view has created and modify its properties. This way we can selectively change properties, but have the standard behavior in general.

    Do we really need an option for this? For reading large tooltips, the tooltip should not disappear that fast, however I don't see a reason for hiding it after some custom time. Why not just display it as long as possible? Dismissing it is easy, by simply moving away the cursor. There are scenarios where automatic hiding makes sense (e.g. for a toolbar button, where the text usually can be read within a second and the tooltip might hide other important controls/content), but for the group tree I don't think automatic hiding is necessary.

    Thus I've now implemented the following: when the tree view handle is created, KeePass obtains the handle of the child tooltip and changes its auto-pop delay to about 30 seconds, which is the maximum (any larger delays are truncated or ignored by Windows).

    Here's the latest development snapshot for testing:
    http://keepass.info/filepool/KeePass_160413.zip

    Thanks and best regards,
    Dominik

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.