Cannot get pressing F3 to activate the add-in
Ouilly opened this issue · comments
Hi kjnh10,
Love the plugin!
I have an issue when initiating/activating the plugin. I cannot get pressing F3 to work. I have to re-add the add-in from the "Add-ins" menu each time I want to use it. It then asks me if I wish to replace the file (with the same file) and then, once i have pressed yes, it works like a charm. Let me know if you want to see any screenshots or outputs, I am happy to provide them.
This could be a me-problem but any help is appreciated as I absolutely adore this add-in as a vim-user and occasional excel-user!
All the best,
Ouilly
Thanks for reporting.
Could you paste screenshots or outputs?
And please tell me about your Excel version.
Thanks,
Hi again,
Not sure if this is useful but here are a few screenshots showing the process i go through to work around the problem in roughly the following steps:
(Edited for clarity)
- Opening Visual Basic in an empty spreadsheet without pressing any buttons
- Pressing F3 and then attempting navigating using 'j' and 'k'
- Navigating to Excel Add-ins
- Re-adding the add-in using 'Browse'
- Confirming the replacement of the file, once chosen
- Navigating with 'j' and 'k' etc. now works
- Visual Basic after the add-in has been re-added
My Excel version is: Microsoft® Excel® for Microsoft 365 MSO (Version 2207 Build 16.0.15427.20182) 64-bit
Not quite sure how to properly show this issue and perhaps only the final image with the Visual Basic output is of any use; however, I hope you have what you need for now at least. Please let me know if you want more pictures or outputs!
Best,
Ouilly
Thanks for the explanation.
I would like to confirm you just want to start using excel, and for that purpose, you pressed F3. Right?
If it's so, you don't need to press F3.
You can just press ctrl + n to open a new book or open some files from the menu bar.
Pressing F3 is for reloading this libarary when you modify the code which are stored in .vb files.
And F3 should not be pressed in the VBA editor, since this tool can't handle the pressed keys in the VBA editor.