Ten Things I Dig About Xcode
Subject:   This is a general problem with the Mac GUI
Date:   2003-10-29 08:55:42
From:   anonymous2
"when you edit multiple files, you ask to compile, you get the window asking to save the files, but hitting enter does not "click the default button" of the dialog. Instead, you have to click manually with the mouse."

I hate to say anything nce about Windows, but in Windows keyboard navigation is a first class citizen, not an afterthought. Regardless of the API you use, what apple calls "full keyboard navigation" is enabled... and it goes far beyond what Apple provides.

I use a Mac at home and Windows at work, and every morning and every evening I go through a frustrating readjustmant. On the Windows side it's the usual "you never know what the h*ll Windows is doing" problems. On the mac it's going back to the "one hand on the keyboard one hand on the mouse" navigation... not only does Apple have lousy keyboard navigation, but if you're mousing around you have to keep your fingers ready for option-click and command-click.

Main Topics Oldest First

Showing messages 1 through 2 of 2.

  • This is a general problem with the Mac GUI
    2003-12-17 13:59:43  anonymous2 [View]

    What are you talking about?
    I can't recreate the problem you describe when using 1.0.1, are you using an early version or something?

    If "enter" doesn't click the default button, the space bar always does...

    besides, what rational reason would you have for not using "always save" when compiling? Use an SCM tool and have XCode save files for you.

  • This is a general problem with the Mac GUI
    2003-12-04 00:41:34  anonymous2 [View]


    I hate mac. Mac sucks sucks sucks in keyboard navigation.
    Windows is the mother of keyboard navigation.

    I wish mac could learn from windows.

    I especially like Alt+<underlined menu items>, which
    is sort of universally works everywhere even if you
    happen to forget the shortcut keys.