Re: key equivalents in Interface Builder Xcode 4
Re: key equivalents in Interface Builder Xcode 4
- Subject: Re: key equivalents in Interface Builder Xcode 4
- From: Brian Gardner <email@hidden>
- Date: Sat, 02 Jul 2011 07:58:25 -0700
Thanks. This makes sense.
Sadly, so many command key equivalents are taken.
And often by tasks that the user seldom performs.
1. Is there a way to resolve the issue of them being double-taken?
The Command-F is standard for both Full Screen and Find text.
The Command-I is standard for both Import and Inspector window (or Info window).
2. Is there a way to recover some of these?
To make them "hot" keys again, instead of "cold" keys -- so the User can be their user.
Oddly, when I remove the Command-I from Import, in IB, and assign it to the Inspector,
it doesn't appear in the menu of *either* when the app runs.
Similar problem with Command-F. If I change Edit->Find to Command-Shift-F,
and assign Command-F to View->Full Screen, in IB, when the app runs, the
Command-F has disappeared from the Full Screen menu item.
Even though Find is now correctly changed to Command-Shift-F.
Instead, if I create a custom class, based on QTMovieView, perhaps
I can recover the Command-F for Full Screen? Feels like IB should do it somehow, though.
-- Brian
On Jul 2, 2011, at 2:57 AM, Christiaan Hofman wrote:
> The main problem you're probably having is that for many views, especially complex views, the view will eat up all kinds of key events before it reaches the menus. This is especially true for key events that have no Command modifier. This is why it is always recommended that you use Command equivalents for menu items.
_______________________________________________
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