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 19:20:29 +0200
On Jul 2, 2011, at 19:03, Brian Gardner wrote:
> Ah. I see.
> When X-Code first created the UI, there were already multiple
> assignments it gave to the same key equivalents, buried in submenus.
>
> It assigned Cmd-I to both Import and Italics.
> And Cmd-F to Find and another (I think it was Smart Copy/Paste) I've since removed.
> So, several duplicate or triplicate key equivalents were automatically assigned.
> The project was automatically initiated with many menus & sub menus (w/ key equivs.)
> which I haven't gotten far enough along with my coding to consider.
>
> Should I be enabling/disabling these, based on context (whether cursor is in image vs text views)...
> or should I just remove/replace all duplicate/triplicate equivalents to be cleaner?
>
No, you generally should not disable them conditionally. When an item is not relevant or important for your app, either remove the shortcut from the menu item or the whole menu item. Note that *you* don't even realize that Cmd-I may mean Italic (in some circumstances), your users will certainly be confused.
Christiaan
> Odd that IB doesn't offer Warnings about duplicate key equivalents being used.
>
> -- Brian
>
> On Jul 2, 2011, at 8:24 AM, Christiaan Hofman wrote:
>
>>>
>>> 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"?
>
_______________________________________________
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