We have a Visual Studio 2010 VSIX / Package that provides a custom ToolWindow but by default the 'Save' / 'Save All' Buttons of Visual Studio are active for instances of this ToolWindow, even though we did not implement any particular code for that.
Now as these Save buttons are enabled, users often think that content displayed and changed within that ToolWindow needs to be persisted by pressing these Save Buttons, however, when another Document-ToolWindow is open in the background (that apparently DOES
implement Save logic), content there is saved.
Now in order to properly handle these Save Commands / Buttons and assigned shortcuts when our toolwindow instances have focus, what would I need to do?
These are not documents per se at least not a source code file or anything stored locally, basically the toolwindow displays data from a database, the user can edit there & persist it back (via a button on the form).
Thanks,
-Jörg