#1242 Selecting text in auto-type sequence always marks two braces at once


When selecting text in the field "user defined auto-type sequence" with the mouse, somehow always two braces are highlighted at once making it very inconvenient to copy/paste content in from this field.

E.g. consider you have "{USERNAME}{TAB}{PASSWORD}{ENTER}" and would want to add a "{TAB}" before "{ENTER}" by copy/pasting the already present "{TAB}".

  • Start highlighting text between the second/third brace with the mouse.
  • Notice (as soon as the selection reaches the "T" of "TAB") how the whole word "TAB" is highlighted (which might be convenient in some cases) but also the second brace gets highlighted in error.
  • Notice (as soon as the selection reaches the fourth brace) how automatically the fourth AND the fifth brace are highlighted.

I don't know which logic is triggered here when selecting, but it's highly inappropriate in the auto-type sequence field. Where one would want to highlight terms enclosed in braces and not the closing/opening braces from the preceding/following specifiers.


  • Paul

    Paul - 2014-05-04

    I suspect it's a Windows thing.
    The behaviour differs depending on what screen you are in. On the Auto-Type tab, override default sequence, double clicking selects the word and the braces.
    Editing a "target window", double click only selects the word, but it's easy to click once where you want the additional place holder and click in the "insert place holder" box.

    cheers, Paul

  • Ede_123

    Ede_123 - 2014-05-04

    Yes, probably. Sorry I forgot to mention I'm on Windows 7 in the first place.

    However I assume this unfortunate behaviour can be disabled somehow? Maybe it's a .Net thing? The only other application were I noticed this selection behaviour so far is Microsoft Office (2010).

    Last edit: Ede_123 2014-05-04
  • T. Bug Reporter

    T. Bug Reporter - 2014-06-02

    This is probably an effect of a so-called "feature" that's built into the text editing tools that are provided by Microsoft. Many of the programs that are built using these tools (including Microsoft Office) provide a means to turn this off for the people (like us) that find it to be more annoyance than convenience; unfortunately, KeePass apparently isn't one of them.

    Another example: if you're using MSIE to view this, and you put your mouse on the "d" in "including" above and click and drag in an attempt to select "ding Microsoft Off", you probably won't be able to do it without a lot of fiddling - and MSIE is an example of a program that doesn't provide a means of turning off this "automatic word selection". (Apparently, they feel that allowing people to override this by spending several seconds fighting with it every time is an adequate solution.) In the opinion of the people who designed this feature, "{PASSWORD}{ENTER}" is five words: "{", "PASSWORD", "}{", "ENTER", and "}".

    I'd like to see KeePass provide an override switch for this (or turn it off completely), but until I read this thread it was very low on my wish list for KeePass.

  • Dominik Reichl

    Dominik Reichl - 2014-06-21

    This is caused by a .NET bug. KeePass never enabled this selection feature, and by default it should be turned off; however, due to the bug it effectively is on by default and cannot be turned off reliably in the straightforward way.

    Fortunately, I found a workaround, and have implemented it now.

    Here's the latest development snapshot for testing:

    Thanks and best regards,

  • Dominik Reichl

    Dominik Reichl - 2014-06-21
    • status: open --> closed
  • Ede_123

    Ede_123 - 2014-06-21

    Thanks! Seems to work reasonable now.

  • Paul

    Paul - 2014-06-23

    The double click method still gives different a result depending on where you use it. On the Auto-Type tab, double click selects the word and the braces either side. When editing a Target Window sequence, double click selects the word only.

    cheers, Paul

  • Dominik Reichl

    Dominik Reichl - 2014-06-23

    True, but there's no option for changing this behavior, and I'm not planning to implement a custom one.

    Best regards,


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks