Opening new content into the existing tab instead of a new tab

Hello

When double-clicking (or single-clicking when "autoscroll from source") on a file, is it possible to open the file in the existing tab instead of opening a new tab every time ?
This is how xcode behaves and I must admit I like that as it doesn't clutter the whole tabbar with various tabs.

thanks for your answers !
Louis

9 comments
Comment actions Permalink

No, this is not possible, AppCode uses a dedicated tab for each file.

0
Comment actions Permalink

Thanks for your answer Anton,
wouldn't this be an intersting feature for a future version of Appcode ?

0
Comment actions Permalink

Louis,
we will consider such a feature.

Thank you for the feedback

0
Comment actions Permalink

Hi Louis,

If your intention is to only have 1 file open at any time (in 1 tab), you can achieve that already.
Go to Preferences -> Editor -> Editor Tabs and set the Tab limit to 1.
That way AppCode will reuse the existing tab whenever a new file is opened.

If you want to hold a specific file open in an extra tab, you can also do that by right-clicking on the tab and selecting 'Pin Active Tab'.
That will keep that tab open while another non-pinned tab takes over as the 'single' tab.

Cheers,
Maarten

0
Comment actions Permalink

I have to say this is one of the things that makes Xcode such a usability nightmare. For example, when you hit a breakpoint, Xcode will open the file with the relevant line in whatever tab you're currently in. This means you can end up with the same file open in multiple tabs. It's true that you can use behaviours to nuance this by setting up dedicated tabs, but it's still a mess.

With Xcode (4), I always seemed to spend much of my time managing the IDE (fighting with it for control over tabs, stopping various silly panes flapping about, etc. With AppCode, I rarely give it a thought: it just feels like a transparent window onto code. It's possible that the two just suit different personal styles, I suppose, but give AppCode's style of tab management a go. My experience (after a few months with it full-time) is that it makes Xcode seem even clunkier than I already thought it was.

0
Comment actions Permalink

Hi Maarten

thanks for the tips, this solves the clutter problem I have after having browsed through a lot of files.

0
Comment actions Permalink

Hey Crispin,
you're right, Xcode isn't perfect from a usability point of view ... I picked up too many bad habits using it.
It's like when i switched from pc to mac > I was tweaking the OS and looking for masses of software to reproduce the environment in which I has to comfy ...

I've been using appcode for almost a month and I must admit I got used to the cmd+e (file history) menu and splitscreen code editor to navigate between classes.

0
Comment actions Permalink

Hope you're enjoying it as much as I am.

0
Comment actions Permalink

I created a forum account just to respond to this post. I *much* prefer the way AppCode handles tabs. Xcode is always destroying my editing context by opening up new items in my current tab. I think the AppCode way might take a little getting used to but honestly I think Xcode 4's behavior makes tabs practically useless.

0

Please sign in to leave a comment.