#1251 Auto-type Title Matching Does Not Recognize "~"

KeePass_1.x
closed
nobody
None
5
2014-06-02
2014-05-31
user2037
No

Trying to auto-type to Cygwin windows containing only "~" fails with Keepass 1.17. It works with Keepass 2.26.

Discussion

  • Paul
    Paul
    2014-06-01

    Works for me, sort of. I created a web page with "~" as the title and used an Auto-Type target of "~*". Both KeePass 1.27 and 2.26 work.

    Maybe your Cygwin title has a white space character in it as well as the tilde. Use the target window drop down selector in KeePass 2 to view the exact title.

    cheers, Paul

     
  • user2037
    user2037
    2014-06-02

    Whitespace should not matter since I also tried star-tilde-star without success. Regardless, I've dropped Keepass 1 for Keepass 2 for the time being.

     
    Last edit: user2037 2014-06-02
  • Paul
    Paul
    2014-06-02

    I suspect it's not matching because the window title isn't really a tilde, it just looks like it. That's why I suggested the target window selector, which is in V2.

    cheers, Paul

     
  • Dominik Reichl
    Dominik Reichl
    2014-06-02

    • status: open --> closed
     
  • Dominik Reichl
    Dominik Reichl
    2014-06-02

    I cannot reproduce this problem with KeePass 1.27. When I create an entry with "~" as entry title, the entry does match the Cygwin window titled "~". Furthermore, when giving the entry an arbitrary title and specifying "Auto-Type-Window: ~" (or ending with ~ or ~*), the entry also matches fine.

    KeePass 1.27 has a target window picker, too; so if you're unsure whether your definition is correct, you can use this: click the 'Tools' button in the entry dialog -> 'Auto-Type: Select Target Window' -> click the drop-down button.

    Best regards,
    Dominik

     
  • Dominik Reichl
    Dominik Reichl
    2014-06-02

    While testing this issue, I noticed that Cygwin's Ctrl+Alt behavior differs from Windows' behavior, which results in some special characters not being auto-typed correctly. For KeePass 2.27, I've now added a workaround.

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

    Thanks and best regards,
    Dominik