AutoTypeSearch Activity
AutoType Quick Search plugin for KeePass
Status: Beta
Brought to you by:
alexvallat
Activity for AutoTypeSearch
-
AlexVallat posted a comment on ticket #1
Congratulations! I still don't think it's the right direction for this plugin, but I am always interested to see what people have done with my code - if you do publish the source please post a link.
-
Humangenom posted a comment on ticket #1
I have done this in my own fork. I can search for any combination of words. They must not be in one field and can be distributed to many fields. If you are interested, I can put it on GitHub.
-
AutoTypeSearch released /v1.6/AutoTypeSearch-v1.6.zip
-
-
Alex Vallat committed [293de6] on Code
Fix bug where search window immediately closes after canceled first show of auto type selection box
-
Guillaume modified a comment on discussion General Discussion
Aha, I knew there had to be some other setting related with all this. Not sure why I enabled "Always show global auto-type entry selection dialog" (years ago), but there must've been a good reason. After so much time I even forgot it was optional to begin with. I just tested the attached version, and all is well now! Thanks so much for your work and quick responses!
-
Aha, I knew there had to be some other setting related with all this. Not sure I enabled "Always show global auto-type entry selection dialog" (years ago), but there must've been a reason and after so much time I even forgot it was optional to begin with. I just tested the attached version, and all is well now! Thanks so much for your work and quick responses!
-
I understand which hotkey you mean now. What I hadn't got was the empty auto-type dialog. This only appears if you have the advanced setting to "Always show global auto-type entry selection dialog" set, and with that I can reproduce the issue. For some reason the search window is receiving the Lost Focus message, I don't know why. I've put in a workaround for the issue, can you give the attached 1.6 candidate a try and let me know if it resolves the issue for you?
-
I understand which hotkey you mean. What I hadn't got was the empty auto-type dialog. This only appears if you have the advanced setting to "Always show global auto-type entry selection dialog" set, and with that I can reproduce the issue. For some reason the search window is receiving the Lost Focus message, I don't know why. I've put in a workaround for the issue, can you give the attached 1.6 candidate a try and let me know if it resolves the issue for you?
-
There I'm making the distinction between 1. The system-wide hotkey for the plugin AutoTypeSearch (which can be specified in the settings tab specifically for this plugin). Accessing AutoTypeSearch via this hotkey shows no problems. 2. The system-wide auto-type hotkey for Keepass's native auto-type. This is where the problem lies. When using this hotkey, then canceling the empty Keepass auto-type dialog, AutoTypeSearch doesn't show up the first time.
-
OK, I think there is something I am not understanding. You say "The system-wide hotkey for AutoTypeSearch does not exhibit this behavior", but then what hotkey are you talking about? The global autotype hotkey is system-wide.
-
Thanks! I suppose there might be another setting involved, but I haven't found a way to not get this issue yet. Some more info: - The system-wide hotkey for AutoTypeSearch does not exhibit this behavior: the dialog is shown the first time I use that hotkey. - I thought that perhaps pressing Escape in the Keypass auto-type window would inadvertently also cause Escape being triggered inside the AutoTypeSearch window that follows, but that isn't the case: pressing the Cancel button in the Keypass auto-type...
-
Hmm, not been able to reproduce this, but I'll try a bit more tomorrow. I'll hold off the 1.6 release for a bit to see if there's a fix for this that should be included.
-
The first time after Keepass is started, it doesn't show anything instead of showing AutoTypeSearch as expected. The second time I try this (as in step 7), AutoTypeSearch does show up. I do some flashing, it's like AutoTypeSearch is minimized or something.
-
The first time after Keepass is started, it doesn't show anything instead of showing AutoTypeSearch as expected. The second time I try this (as in step 7), AutoTypeSearch does show up.
-
At step 5, I see AutoTypeSearch appear. Which window do you see appear? If there are 0 matches, it should either show AutoTypeSearch (if configured to do so), or nothing at all.
-
Enable the following settings Keepass: Minimize main window after opening a database AutoTypeSearch: Show automatically if global auto-type finds no match Close Keepass Re-open Keepass and open a database Press the global auto-type hotkey in a window that will result in 0 matches (e.g. Notepad) Close the Keepass auto-type window See that AutoTypeSearch doesn't open Repeat steps 4 & 5 See that AutoTypeSearch now does open If this doesn't reproduce the issue, it's probably necessary to automatically...
-
Enable the following settings Keepass: Minimize main window after opening a database AutoTypeSearch: Show automatically if global auto-type finds no match Close Keepass Re-open Keepass and open a database Press the auto-type hotkey on a window that results in 0 matches (e.g. Notepad) Close the Keepass auto-type window See that AutoTypeSearch doesn't open Repeat steps 4 & 5 See that AutoTypeSearch now does open If this doesn't reproduce the issue, it's probably necessary to automatically open a database...
-
Oh, well spotted. Thanks for reporting it. This should fix the issue.
-
Alex Vallat committed [ffc82e] on Code
Fix bug with Enter key press detection
-
luday posted a comment on discussion General Discussion
Thanks for uprgats it. Unfortunately I have tried it and I have some problems with some characters when I am typing on my keyboard "o" "O" "m" "M" "^" "/" ":" "!" "§" the search window closed. I try to copy it or type with alt+79 for the "O", I don't have any problem.
-
Thanks for doing the merge request. I've merged it, and added a few tweaks. I moved the drawing of the shortcuts over to the bottom right so they aren't as squashed up to the bottom, and made it only appear after you first use any modifier so it doesn't distract when unwanted. Also made the drop downs in the options a bit bigger to fit all the text. If you'd like to give the 1.6 candidate a try, I've attached it here. I'm giving it a bit more testing and will release soon, unless you find any problems...
-
Alex Vallat committed [1a6a0d] on Code
Prepare for v1.6 release
-
Alex Vallat committed [03afce] on Code
Resolve VS warnings/messages
-
Alex Vallat committed [76d49c] on Code
Fix Options for designer, tweak layout of new action options with table layout panel
-
Alex Vallat committed [4409ab] on Code
Improve position of modifier message by self-painting, move timer into designer, refactor modifier key evaluation for common code
-
Alex Vallat committed [fedc3c] on Code
Sync designer.cs with settings file
-
Alex Vallat committed [995ed0] on Code
Provide upgrade path from previous settings
-
AddShortCut
-
AddShortCut
-
I think that UI looks better, thanks. You wouldn't have permission to merge, but you should be able to create a merge request - do you see a button called "Request Merge"? That should then create a merge request which I review and approve. (example)
-
hi, i create the fork with new the UI modification and i having try to dispay message indicate which action under the message "Start typing to search entities". Maybe we can also put it on the selected ligne. I try to merge but i can have permition to do i think.
-
Thanks. I like the UI modification for the additional actions. For the other change, in principle the idea of having a message indicate which action will be taken with the currently held modifier keys seems good, but I don't like having it in the same label as the "Start typing to search entities" message. I'll try and think of another place for it; if you have any other ideas for how to present it, please let me know. If you create a fork and a merge request then I'll review the code. The advantage...
-
Hello, I use your plugin and I like it. I added some features if you're interested. In particular, I added an additional shortcut, and I also displayed a message to indicate which action will be used when confirming by pressing Enter. I think i can create a new git branch from your project, but I'll leave you the files I've modified if you are intersted. Maybe the default value variable was not the best.
-
ptron posted a comment on discussion General Discussion
Yes, you are right that my workflow is somewhat different than what seems to be that of most KeePass users, who it seems go first to a web page (by whatever means), and then proceed to enter credentials, which fits with KeePass auto-search/type. Whereas my usual workflow has been first to select the account in the password manager (Obliette) and use its go-to-url shortcut to open the web page. Then use Oubliette's global hotkeys to enter username and password. So I was looking for something similar...
-
I hadn't read that one. I can't think of a solution without modifying the auto-type sequence, but you can do that quite easily by setting the default auto-type sequence for a whole group. If you right click on a group and choose Edit Group, then the Auto-Type tab, you can set a default auto-type sequence for all entries in that group. You could then use something like AutoTypeSplitter to insert a message box between the username and password parts of your sequence, that would let you wait until the...
-
Alex, thanks for sticking with this. That plugin was actually the first mentioned to me in a query on the KeePass discussion forum: First Impressions. My call above for a new plugin was not aimed specifically at you, but at any prospective developer who thought it was a good idea. But it did seem a little like just a stripped-down version of yours :-) !
-
Ah, I get what you mean now. It's not exactly what you are asking for, but KPEnhancedEntryView will let you click on any field of an entry and click Ctrl+V to auto-type it. So you could select an entry, click on the User name field, and then Ctrl+V and it would auto-type it.
-
Thanks for the suggestion, but I've already tried that plugin. It, too, depends on selection criteria, rather than simply the currently selected account. I've searched and searched, and as far as I can tell, the entire KeePass ecosystem seems to rely wholly upon that criteria, which is the reason for my call for a plugin which would provide current-account functionality, rather than selection criteria (as an addition, not a replacement).
-
-
-
Alex Vallat committed [c7b2de] on Code
Add Perform User Name Auto-Type action
-
Alex Vallat committed [48b634] on Code
v1.5
-
I'm glad it's working, thanks for letting me know. You only need one of the plgx or the dll in the directory, not both. For the other plugin you want, try https://github.com/Rookiestyle/AdvancedAutoType, I think that will do what you need.
-
Okay, so after some experimenting with deleting and clearing and so forth, I have the new (1.5) version installed, and it is doing exactly as requested! Thank you, Alex, that is great! One question: does the .dll need to be in the plugin directory, or just the .plgx, or both? Here is a suggestion, and this is not aimed specifically at Alex, but at any plugin developer who might be interested: I would like a simple plugin which would provide two global (user-defined) hotkeys, one of which would send...
-
Okay, so after some experimenting with deleting and clearing and so forth, I have the new (1.5) version installed, and it is doing exactly as requested! Thank you, Alex, that is great! One question: does the .dll need to be in the plugin directory, or just the .plgx, or both? Here is a suggestion, and this is not aimed specifically at Alex, but at any plugin developer who might be interested: I would like a simple plugin which would provide two global (user-defined) hotkeys, one of which would send...
-
You should only have one, but if it's causing confusion I've generated the .zip release which has both. Choose either .dll or .plgx, and put that in the plugins directory. I'd suggest moving the old ones out entirely (or deleting them) rather than renaming them, I'm not 100% sure how KeePass deals with plugin file extensions. The original recommendation was to use plgx, but recently (in the last few months) KeePass recommend using .dll instead now. Either should work. If you still see no difference,...
-
Wow, Alex thanks for the quick turnaround! Unfortunately, I don't see any difference with this version--though that is likely because I've not set it up correctly. In the KeePass plugin directory, I previously had AutoTypeSearch.dll and AutoTypeSearch.plgx. I renamed those (to hide them), cleared the plugin cache, copied the new AutoTypeSearch.plgx into the plugin directory and restarted KeePass. That didn't work, so I added back the AutoTypeSearch.dll as well. But still no change; it is exactly...
-
Please give the attached v1.5 preview a try and let me know if it does the job for you
-
Thanks for the suggestion. Sure, why not, I'll add that.
-
It would be helpful to have 'Perform user-name auto-type' added to the Default action menu and the Alternative action menu. With 'Keep search window open' checked, this would allow the user to quickly fill each of those two fields on demand. While not as convenient as full auto-type, it would solve many edge cases.
-
I think if you have AutoTypeSearch.dll as well as AutoTypeSearch.plgx then the dll takes priority, so delete the dll and the plgx should be used. If you do an autotype into a window that either fails to match, or shows the multiple matches window that you then cancel, then AutoTypeSearch will appear with a small yellow banner at the top telling you the title of the window which wasn't found. If that banner doesn't appear then AutoTypeSearch wasn't triggered through an un-found window, and so it won't...
-
Dmitry posted a comment on ticket #12
Thanks, Alex. However, I wasn't able to see how this works. I didn't see any options to add the window title to the entry when using AutoType. Could you provide a screenshot or explain what settings are needed to make this work? Maybe a new version of AutoTypeSearch.dll is required?
-
Thanks for the detailed explanation. I still believe having the prompt after performing the AutoType from the search window is the best way to handle this. I will not add any additional UI to the search window in any case. I do take your point that this currently does not work for the case where KeePass shows the multiple matches window and you cancel it because none of them are the right one. This logically also counts as a failed auto-type and shows the AutoType Search window, so it should also...
-
Hi Alex, Sorry for the late reply. Here are the details to clarify my proposal: Current behavior on my setup when pressing Ctrl + Alt + A (option "Show AutoTypeSearch automatically if global auto-type no match" is turned on): If the current window is not found in any KeePass entries, the AutoTypeSearch window appears, and we manually search for the needed entry. If the current window is found in one entry, auto-type works (Yay!). If the current window is found in more than one entry, the global auto-type...
-
Clément Baudouin posted a comment on discussion General Discussion
Thanks, I had the same issue. The option "Always show global auto type entry selection dialog" is under the "Auto-Type" section in the Advanced tab of Keepass settings. And unchecking that solved it.
-
Sorry, I don't understand what you are asking for here. If you perform auto-type into a window and it fails, it should offer to save that window title to the entry because it knows you were expecting auto-type to work for that window and it did not. If there isn't an attempt to auto-type then I don't think AutoTypeSearch should offer to add the title, as that could get quite irritating if your workflow is just to use search and not autotype (probably because you know the window title isn't helpf...
-
Is there any possibility for the plugin to get information about the title at the moment of pressing Ctrl + shift + A, so that then (even if the focus is changed to the AutoTypeSearch window), you can use the previously obtained window title for saving and richness in the record?
-
-
-
Alex Vallat committed [2fae93] on Code
Ensure title gets reference resolved when option enabled
-
Alex Vallat committed [9d083f] on Code
Release both plgx and dll
-
Alex Vallat committed [b783d4] on Code
v1.4 Offer to save the window title as an auto-type target
-
Stewart Anderson posted a comment on ticket #13
Brilliant, I hadn't seen that. cheers :) Stewart ------ Original Message ------ From "AlexVallat" alexvallat@users.sourceforge.net To "[autotypesearch:tickets] " 13@tickets.autotypesearch.p.re.sourceforge.net Date 14/06/2023 19:03:27 Subject [autotypesearch:tickets] #13 De-Reference/ Resolve variables in teh search window I've looked into this a bit. There is already an option "Resolve field references" in the AutoTypeSearch options tab, so the fact that this is not resolving the title field for...
-
I've looked into this a bit. There is already an option "Resolve field references" in the AutoTypeSearch options tab, so the fact that this is not resolving the title field for you is a straight bug. I will fix it up, probably this weekend.
-
Ok. It does impact performance a bit, even in the main window. Keepass notes this in the settings, but I use it anyway. I use references in the title often where I have set up variables like environment amongst other things for dev/test/prod where I use the entries as launchers to different environments. Its not a problem. Was worth asking. TY for coming back to me. Stewart ------ Original Message ------ From "AlexVallat" alexvallat@users.sourceforge.net To "[autotypesearch:tickets] " 13@tickets.autotypesearch.p.re.sourceforge.net...
-
I can look into this, but only if it can be done without compromising performance. Can you give me a bit of context for the use case here, which field is it that you have the reference in, and what sort of reference is it? What were you expecting to see?
-
De-Reference/ Resolve variables in teh search window
-
That makes no sense as I have Google Mail in a thousand other notes and I don't find what I want. And this is just one example. This happens with many different searches also.
-
Your title is "Google Mail" and you searched for "googlemail", which only appears in the notes. Try searching for "google mail" instead (or alternatively edit the title to remove the space)
-
Nope as it shows the notes first and I don't see anything there
-
If you have many entries with the title "Googlemail", and you search for "Googlemail", the results should already list the username (below the title). It is only if the search term is found somewhere other than the title that the field in which the search term was found is shown instead of username.
-
If you have many entries with the title "Googlemail", and you search for "Googlemail", the results should already list the username (below the title). It is only if the result is found somewhere other than the title that the field in which the search term was found is shown instead of username.
-
I have many entries e.g. only Googlemail and username is different. I have a lot of infos and when I search for googlemail I get the results but don't see which entry is which user. I solved it for my by adding always the username when drawing the title. Instead of only searchResult.Title I use searchResult.Title + " - " + searchResult.Entry.Strings.ReadSafeEx( PwDefs.UserNameField ) Could you add an option to always show the username in the title?
-
The request will not happen if it isn't searching for a window title. So if you have just used the hotkey and searched for an entry, rather than having it appear automatically because the target window was not found, it won't have a window title associated with the search.
-
Thank you for feature! Sorry for late reply. Already test it, generally works, but sometimes the request to save windows doesn't happen. I dont know why. There is a suspicion that this happens if the selected entry already has target windows (but they did not work, for example, if the site changed the title), But this also may not work on recordings where target windows have not yet been configured.
-
Please give the attached 1.4 candidate a try. I decided that instead of a checkbox it should show a message asking if you want to save the window title as an auto-type target. This should not be something that happens silently, but require a positive user confirmation each time - whether a window title is a sensible target for an entry is a decision that needs to be made every time. There is a "don't ask again" checkbox on the message which will disable the feature.
-
Thank you for the suggestion, this makes sense to add as an option. I will try to add it when I have time.
-
Feature (Chekbox) - add current Title-windows to auto-type for selected entry
-
Dave modified a comment on discussion General Discussion
KeePass update check always fails for AutoTypeSearch. Update: Never mind, I found a previous thread about installing SourceForge updatechecker.
-
KeePass update check always fails for AutoTypeSearch. Can this be fixed?
-
-
-
-
-
Thank you for the PR. I decided to go a different way with the fix for autotype, there were just too many edge cases with the ActiveForm solution in your PR, so I just went the simple way of hiding and then re-showing the SearchWindow, if it's visible. I still prefer to have a single option that keeps the window open until manually closed, I think that covers all use cases of why people might want the window left open without trying to configure each one individually.
-
Alex Vallat committed [450242]
Revert search window blank space from previous commit
-
Alex Vallat committed [63e667]
Fix issues introduced by 1.2
-
zoidy modified a comment on discussion General Discussion
Hi, I've opened a merge request on Sourceforge. I've added the ability for the user to separately control whether the search window closes after executing the primary or alternative action. The options are off by default which replicates the existing behavior. Hopefully this will avoid confusion. Additionally, the window focus should behave more like the current version of the plugin. When one of the new options are enabled, the window will close when it loses focus unless the corresponding primary...
-
Hi, I've opened a merge request on Sourceforge. I've added the ability for the user to separately control whether the search window closes after executing the primary or alternative action. The options are off by default which replicates the existing behavior. Hopefully this will avoid confusion. Additionally, the window focus should behave more like the current version of the plugin. When one of the new options are enabled, the window will close when it loses focus unless the corresponding primary...
-
Ability to close the search window after executing action
-
-
-
Alex Vallat committed [221961]
Add "Keep Window Open" option
-
Alex Vallat committed [b270b2]
Add "Copy user name" action
-
Alex Vallat committed [ee1636]
Bump version number to 1.2
-
Alex Vallat committed [471574]
Add (hidden) text title to search window
-
Thanks, that looks good, but I think it might be a bit confusing that the primary action doesn't close and the secondary one does. Also, it won't automatically close on loss of focus either (logical, as you wouldn't be able to paste the username in without having it close otherwise). Perhaps it would be better to have the option as just "Leave window open", and the user has to click escape to close it once they've finished? That way it doesn't matter if they use the primary or secondary action first,...
-
I have the following use case: It is sometimes useful to copy both the username and password instead of autotyping (e.g., if the password field doesn't show up until after the username is entered, or if one uses a remapped keyboard which causes autotype to enter the wrong characters) I have added these functions to AutoTypeSearch * The ability to copy the user name as a default or alternative action * The option to leave the search window open after executing the primary action. This enables setting...
-
I don't want to have advanced search. if I have Username: xyz Info: abc I want to find this entry. Just search for each part in all fields and if all parts are found, it's a match.
1 >
