| OK, I think I get it now.
• Open a .m source file • Click on Show the Assistant Editor - Shows the corresponding .h. • Command-click on a symbol in the .h (for example NSObject to show it’s interface) • Click on Show the Standard Editor to dismiss the Assistant editor. • Select a totally different .m file from the file tree. • Click on Show the Assistant Editor - Shows NSObject.h
Leaving the Assistant editor open, If I don’t navigate away from the corresponding file, I can click on any file in the file tree and it will always show the correct corresponding file. It looks like if I ever navigate away from the corresponding file in the Assistant editor, I can never see the corresponding file for any other file automatically, unless I click on the X button to dismiss Assistant editor. So clicking X does something different than Show Standard Editor which is a little confusing.
As a suggestion, it would be really nice to have a button/preference that is ‘Show corresponding file always’ rather than sometimes. I’m only interested in seeing the related files rather than keeping a history of previously browsed files. Sorry for going on about this one feature, but it’s something I use on a daily basis and I’m always amazed how hard it is to do.
Doug Hill
On Jul 14, 2015, at 11:56 AM, Scott Ribe < email@hidden> wrote:
On Jul 14, 2015, at 12:49 PM, Doug Hill < email@hidden> wrote:
1. When editing a file I click on the Assistant editor button (e.g. the overlapping circles), and I expect to to see the corresponding .h or .m/.c/.cpp. However it often shows some other totally non-related file, possibly the previous file that was shown there. Dismissing the Assistant editor by clicking the ‘X’ button and clicking Assistant editor again shows the correct corresponding .h/.m/.c/.cpp.
There's a popup menu up there from which you can select "counterparts". As long as you select files by clicking them in the files tree on the left, it will automatically open the counterpart in the assistant editor. But as soon as you do something else which results in breaking that pairing, it doesn't until you set it back.
|