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: Christiaan Hofman <email@hidden>
- Date: Sat, 02 Jul 2011 17:24:05 +0200
On Jul 2, 2011, at 16:58, Brian Gardner wrote:
> 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?
>
Generally, no, you just need to try to avoid it.
> The Command-F is standard for both Full Screen and Find text.
I would say Cmd-F is standard for Find. Not for Full Screen, which has many different shortcuts in various apps, I think Shift-Cmd-F is much more common for it (as Find is a much more common command, so it will take Cmd-F).
> The Command-I is standard for both Import and Inspector window (or Info window).
>
These are not really standard commands. Therefore what Cmd-I does really does depend on the context, i.e. the app you have.
Generally, the more important commands (most used) for your app should get the simplest shortcuts. So if you want to have both Import and Inspector, you should use the one that is typically used most for Cmd-I and the other for Shift-Cmd-I.
> 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.
>
That depends on why they're not working. If some control takes away the shortcut because of a keyEquivalent there is no way to override, as that will always be the first thing the system tries (and when there are multiple views with the same keyEquivalent you're in trouble, as the assignment will become arbitrary).
> 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.
What do you mean with "doesn't appear"?
And does it appear somewhere, perhaps in a contextual menu?
>
> 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.
>
As I argued above, it seems more natural to do the opposite assignment in general. Is Cmd-F anywhere in any menu, including contextual menus?
I am not sure what is going here, I don't have enough information.
Christiaan
> 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