You might need to adjust the delay for your system, but whatever is going on with Chrome failing to see simulated keystrokes, this seems like it should be all you need to add to get around it.Īs for the OK button appearing randomly, there's a macro-based way to handle that too. In my tests, 0.2 seconds was sufficient to make macro-based EWC activation work, while 0.1 seconds failed consistently. I have no idea why Chrome doesn't register the macro/BTT-based keystroke to activate the EWC immediately, but I was able to figure out a workaround: just add a delay at the start of the macro. Is there any reason it would be a Chrome issue? How could Chrome 'see' where the keyboard shortcut comes from: the EWC itself, KBM or BTT? To see if the problem stems from KBM or Chrome (for whatever reason), I created a BTT gesture to trigger the EWC shortcut, and ended up with exactly the same problem as with KBM. I tried different keystroke combinations and could not make it work. As I mentioned, this happens after a few uses, not the first times, so it's unpredictable.ģ- even stranger, I am unable to create a KBM macro shortcut which would in turn activate the EWC by typing the EWC shortcut. The only irritant is that I have to click on OK each time. Although I get a pop up message, the EWC still works. I tried different web sites and I get popups irrespective of the web site. Never any problem.Ģ- I can activate the EWC by typing the hotkey defined within the EWC in Chrome (as per your instructions), but after a few times, i get a pop up message, as per snapshots below. Hi, funny thing, I encountered 2 problems.ĮWC = Evernote Web Clipper Browser = Chromeġ- I can activate the EWC by clicking on the elephant icon in the toolbar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |