| T O P I C R E V I E W |
| Harald Krause |
Posted - Jul 17 2024 : 2:10:04 PM
Open corresponding file via ALT O does not work anymore, Visual Studio 2022 and latest VA.
It works via the toolbar.
Is there somewhere to check the keyboard bindings? I did not find anything in the settings. |
| 17 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Oct 18 2024 : 12:32:54 PM
Interesting, I did not know about that. Thank you.
On a quick test, there are some places this doesn't work, where Alt-O does work, but they are more edge cases that a lot of people won't run into. |
| jakeslade |
Posted - Oct 18 2024 : 10:30:06 AM
This functionality is available by default in Visual Studio. You don't need VAX for it. Go to Tools -> Options -> Environment -> Keyboard and then search for "EditorContextMenus.CodeWindow.ToggleHeaderCodeFile" and you can select the bind as desired. By default it is Ctrl+K,Ctrl+O.
Hope this helps. |
| feline |
Posted - Oct 02 2024 : 09:30:27 AM
So much for that theory. This is odd, I would not expect the problem to happen under these conditions. Certainly this isn't normal, but I am not sure what to make of this. |
| Harald Krause |
Posted - Oct 02 2024 : 07:50:27 AM
Its set on "Default". |
| feline |
Posted - Oct 01 2024 : 10:11:33 AM
Thank you for explaining. I have installed these components, on a clean VS2022 install, under Windows 10, and then installed VA 2530 for the first time, and Alt-O works just fine.
So what ever the trigger is for this, it isn't quite that simple.
Definitely a bit surprised you are seeing this on a clean install, rather than an upgrade though.
If you have a few moments, can you please go into:
IDE tools menu -> Options -> Environment -> Keyboard
and see what you have the pull down list "Apply the following additional keyboard mapping scheme" set to? For me, this is "(Default)". I have this feeling that this setting might be a factor, but cannot find any notes to confirm that so far. |
| Harald Krause |
Posted - Sep 30 2024 : 12:49:59 PM
In the VS Installer you can choose which Buildtools, sometimes named "Komponents", should be installed. By default only the VS2022 are installed. In "Komponets" they are named like "MSCV v140 - VS 2015 C++ Buildtools (v14.00)" |
| feline |
Posted - Sep 30 2024 : 12:38:01 PM
What do you mean by BuildTools? I am not seeing anything called this in VS2022 extension manager, looking for new extensions to install, or as components to install for VS2022 its self. So I am wondering if I am using the wrong search term? |
| Harald Krause |
Posted - Sep 30 2024 : 09:40:21 AM
It is a new computer with freshly installed Windows 11. So Visual Studio was also a fresh install, however I installed all the Buildtools from VS2015 onwards so it can compile natively VS2015, VS2017, VS2019 Projects... Maybe this causes it. |
| feline |
Posted - Sep 30 2024 : 08:01:52 AM
That is interesting. I do a lot of fresh installs, it is a normal first step in setting up a new tests for anything "odd", and this is not a problem I see. So I wonder if your default IDE settings, possibly imported from your Microsoft profile for Visual Studio, are a factor.
This can certainly happen, but until now I have only managed to reproduce it under quite specific conditions, involving an IDE upgrade. |
| Harald Krause |
Posted - Sep 29 2024 : 9:01:44 PM
Here is an update: Did a fresh install of the latest VS2022 and Visual Assist. Same Problem. Could be fixed with VAssistX -> Help -> Keyboard Shortcuts |
| feline |
Posted - Jul 23 2024 : 08:39:05 AM
We do have the command:
VAssistX -> Help -> Keyboard Shortcuts
to check the keyboard mappings, but when this bug was first reported, people reported mixed results using this dialog. Under "normal" conditions a mapped keyboard shortcut should only disappear if someone has gone in and deleted it, which is a deliberate action.
Unless you are seeing a problem with disappearing keyboard shortcuts? |
| foxmuldr |
Posted - Jul 22 2024 : 08:50:49 AM
Could you add a startup option that would validate the VAX key definitions are still in tact from the last time Visual Studio was shut down? It could notify of any changed keybindings.
--
Rick C. Hodgin
|
| feline |
Posted - Jul 19 2024 : 1:26:42 PM
Strange, I would have expected global scope to work as well. Then again, we need the text editor scope so that we know the command is tied to the current open file in the text editor. I am glad you have this working again, apologies for the problems. |
| Harald Krause |
Posted - Jul 19 2024 : 08:58:44 AM
It seems I fixed it. It was assigned as "Global" not "Text Editor".
In IDE tools menu -> Options -> Environment -> Keyboard I did a reset to "Visual Assist" and then assigned it again. |
| feline |
Posted - Jul 19 2024 : 06:20:26 AM
That is really strange. I have just double checked, and the settings file restores the keyboard mapping for me, using VS2022 version 17.10.4
In the IDE options dialog keyboard settings, if you go to the VAssistX.OpenCorrespondingFile setting, what scope is this set for? For me, when I select it, the shortcuts pull down list shows:
Alt+O (Text Editor)
where Text Editor is the part of the IDE where this keyboard shortcut is active. Is the "shortcut currently used by" pull down list at the bottom enabled or disabled when you have this entry selected? You can have several different commands mapped to the same keyboard shortcut. If this happens, they will be listed here.
Can you please export your VA and IDE settings and send them to me:
VA Options -> Performance -> Export Settings
IDE tools menu -> Import and Export Settings -> Export selected environment settings
I can then import them here and see if I can reproduce the problem.
Please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up. |
| Harald Krause |
Posted - Jul 18 2024 : 3:12:20 PM
Both Methods dont work. Importing the vssettings gives this error Message:
Die Einstellungen wurden mit einigen Warnungen importiert.
Warnung 1: Tastatur: Der Bereich "Text Editor" ist nicht vorhanden. Der innerhalb dieses Bereichs gebundene Befehl "VisualAssist.OpenCorrespondingFile" wird ignoriert.
However in IDE tools menu -> Options -> Environment -> Keyboard -> VAssistX.OpenCorrespondingFile is shown als mapped to ALT O. But it does not work
|
| feline |
Posted - Jul 18 2024 : 07:33:41 AM
Some combination of IDE version, your specific settings, having VA installed, and then upgrading your VS2022 version can cause this keyboard mapping to disappear, which is probably has happened here.
If you look at:
IDE tools menu -> Options -> Environment -> Keyboard
and search for the setting:
VAssistX.OpenCorrespondingFile
you will probably find that this is no longer mapped to Alt-O, so you will need to remap this.
Alternatively, you could save out the following code as the file "vs2022_alt_o_keymapping.vssettings" and then import it via:
IDE tools menu -> Import and Export Settings -> Import selected environment settings
to remap this setting:
<UserSettings>
<ApplicationIdentity version="17.0"/>
<ToolsOptions><ToolsOptionsCategory name="Environment" RegisteredName="Environment"/></ToolsOptions>
<Category name="Environment_Group" RegisteredName="Environment_Group">
<Category name="Environment_KeyBindings" Category="{F09035F1-80D2-4312-8EC4-4D354A4BCB4C}" Package="{DA9FB551-C724-11d0-AE1F-00A0C90FFFC3}" RegisteredName="Environment_KeyBindings" PackageName="Visual Studio Environment Package">
<Version>17.0.0.0</Version>
<KeyboardShortcuts><UserShortcuts><Shortcut Command="VisualAssist.OpenCorrespondingFile" Scope="Text Editor">Alt+O</Shortcut></UserShortcuts></KeyboardShortcuts>
</Category>
</Category>
</UserSettings> |
