One of the most suggested features for Tabs Studio is to automatically open corresponding files (e.g. when Class.cpp is opening automatically open Class.h). It is also one of the hardest to make right. More than a year ago Andreas Guenther wrote the first implementation of this extension and after numerous private tests and a lot of feedback I present you AutoOpener.
The AutoOpener add-in uses the same infrastructure that shows Open commands when you right click on a tab and in the core of the TabsStudio.Connect.OpenCorrespondingFile command. Usage of AutoOpener indicated that liberal default tab grouping options (letting files with any extension to be opened) cause strange errors from Visual Studio when opening a code file that happens to share the same name with a project or a resource file. These errors are fist of all puzzling (strange error code after just double-clicking a file) and then require to manually add excluding rules (for project and resource files) to title or path grouping options. To make AutoOpener behavior more predictable I’ve added the explicit list of extensions that are considered for opening:
You can add and remove extensions from this list going to AutoOpener options, but note that if an extension is blocked for grouping in Tabs Studio options it will not be opened automatically no matter if it on AutoOpener‘s list or not.