Re: Xcode 3.2 usability
Re: Xcode 3.2 usability
- Subject: Re: Xcode 3.2 usability
- From: Chris Espinosa <email@hidden>
- Date: Tue, 1 Sep 2009 12:49:37 -0700
On Sep 1, 2009, at 12:28 PM, Quincey Morris wrote:
1. AFAICT, the documentation window is now *always* disabled in
Xcode's dock icon menu. This means (for example) if you've turned
"Minimize windows into application icon" in System Preferences, you
can't get the documentation window back via the dock. Bug?
Bug. Xcode Preferences is also grey, and some other windows (such as
Repositories) aren't listed at all. This is a late regression in Snow
Leopard that we didn't catch; please file a bug report.
2. The behavior of Command-` has apparently changed. [This may be a
system-wide in Snow Leopard, but I only care about the Xcode
behavior.] Previously, Command-` sent the front window to the back,
which was useful with multiple overlapping windows in the following
common scenario: If the front window is a text editor, Command-`
would reveal the text editor window lurking behind it, even if it
wasn't the next window. Then a simple click would bring that window
to the front.
With the new behavior, Command-` often brings a project or other non-
editing window to the front, requiring a *variable* number of
Command-` actions to get to the next text editor window, and that
requires considerably more UI brain power.
I can't find any Xcode function to bind to a key combination. Is
there one in there somewhere that I missed? Or has anyone got any
suggestions (other than "quit whining about it") for an alternative
that's as convenient as the old way of doing it?
This is a behavioral change in NSWondow, and is now consistent across
all Cocoa applications, including Finder. There were 20 duplicates of
the bug complaining about the inconsistent behavior across
applications; so far there are fewer complaining about the changed
behavior. If you have suggestions, file a bug report and cite <rdar://problem/6582437
> Command-` isn't useful for sending the frontmost window of a stack
to the back anymore.
3. IB has always been a bit flaky about respecting the Space to
which it's assigned. (In Spaces, I have Xcode permanently assigned
to one Space, and IB permanently assigned to a different space.)
Since Snow Leopard/IB 3.2, it's seems flakier. AFAICT, if you double-
click on a XIB file in the project window in Xcode, and IB 3.2
doesn't have any windows open apart from its inspectors, the file
will open in Xcode's Space instead of the Space that IB is assigned
to. Bug?
Yes, known as <rdar://problem/5717952> IB & Spaces Conflict.
Chris
_______________________________________________
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