Re: Xcode 4 UI customizability curiosities
Re: Xcode 4 UI customizability curiosities
- Subject: Re: Xcode 4 UI customizability curiosities
- From: "Andy O'Meara" <email@hidden>
- Date: Tue, 22 Jan 2013 15:49:44 -0600
On Jan 22, 2013, at 1:54 PM, Quincey Morris wrote:
> On Jan 22, 2013, at 11:04 , Andy O'Meara <email@hidden> wrote:
>
>> Apologies in advance if I'm being a meathead here, but is there any way for Xcode 4.5 to bring an already-open file (as a tab) to the front rather than Xcode always make a new tab?
>
> … when you do … what?
Well, when you do a navigation click that initiates a new tab (as set in the general prefs pane). Pretty common unless you do all your editing in a single tab the entire time.
>
>> The other thing that's surprising is that there's no way to remap the option/command/shift combos for click navigation (in the general prefs pane). every other possible thing/key/action in Xcode can be rebound (which is most excellent!), yet the cornerstone navigation mod keys can't? anyone endeavored to hack or workaround this apparent limitation? i feel like it would be a day's worth of work (minus QA) for an apple engineer to have those mod keys be re-mappable.
>
> It's a design decision, and I doubt there's much chance of it changing. The behavior of the option key is reserved consistently to mean "do this in the assistant editor rather than the main editor". Therefore, there's no opportunity to remap using option key combinations. (Within the universe of navigation functions, I guess I mean. There are non-navigation functions that use the option key normally, and I assume you can remap those.)
>
> On the one hand, it's terribly convenient to know that adding the option key to another shortcut will use the assistant editor. On the other, it is burdensome because there are so few available shortcut key combinations.
>
Well, I'm not sure about your logic here since basically every other action can be remapped via the key bindings pref pane (so why are one set of mod keys hard-coded while most other key bindings aren't). But even beyond that, all the stuff you're saying seems to be n/a since in making the nav mod keys re-mappable, it's up to the user to decide what they think is burdensome or not.
Perhaps I'm just in a dying minority of old-school MacOS-influenced (ie. not OS X) people who ask the logical questions and let those answers drive the design rather then accepting 'this is how it is and is good enough (or is too much work)'. and in this case, when the work can be measured in a couple man-days and when having 10 tabs each open with 'MyFile.cpp' is supposed to make any kind of intuitive or intelligent sense. I don't mean to be harsh here -- just trying to share what seems to be screaming at me, ya know? :)
Andy
_______________________________________________
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