Re: Xcode - An Apple Embarrassment
Re: Xcode - An Apple Embarrassment
- Subject: Re: Xcode - An Apple Embarrassment
- From: Rick Mann <email@hidden>
- Date: Wed, 29 Feb 2012 23:35:07 -0800
On Feb 29, 2012, at 19:50 , Brian Barnes wrote:
> If you have a tab open, and click the file in the navigator, it will open over that tab; if you double-click, it will open in another tab EVEN if the original already exists.
>
> The solution is to just do it the same way NetBeans, Eclipse, and Visual Studio do it. A double click to open a file. If the tab exist, bring that tab to the front. If it doesn't, create a new one. Or give us that option in preferences. The tabs containing the navigation pane (and changing it when they are changed, also in radar) and the weird way it creates tabs are so completely different from other environments that it's quite bizarre the behavior ever got in there :)
This is what I've been most bothered about in Xc4. I've written several bugs about it. I think of it as a document-window binding. That is, a document should "belong" to a window (and vice-versa).
Note that "document" is used loosely. Of course, source files are actual documents, but you can also think of an execution context as a document in this concept. For example, if I debug my app on one device, that should open a debug-specific window (or bring said window forward). That window should remember its shape and position. If I debug my app on the sim, a *different* debug-specific window should open (or come forward).
My project is yet another document...
--
Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden