Xcode team, does this item mean that I'll be able to close a project
that has only had UI changes made to it (like different windows are
now open than when I opened the project) without Xcode telling me
that the project has changed and it's not checked out? In other
words, I'll no longer have to check out the .pxbproj just so Xcode
can update the .pbxuser, then revert the .pxbproj? It will be a day
or so before I can get around to installing and using 2.3, but I'm
eager to know if this annoying bug has been fixed.
•Xcode is better about notifying users that a read-only project has
been changed when closing it.
And, thanks a bunch for these:
•A checkbox has been added to the clean confirmation sheet
labelled “Also Clean Dependencies”.
•Improved support for processing Info.plist files
•Compile, Preprocess, and Show Assembly Code menu items now work
with multiple file references selected.
•Better tracking of breakpoints across projects
•Double-clicking on a stack frame will take you to that function in
a separate editor.
•Variable format settings, hex/decimal/OSType etc, are remembered
across debugging sessions.
•Fixed a bug that caused Fix & Continue to fail if distributed
builds were enabled.
•Option-double-click now works on symbols names in documentation
windows.
•Command-E (Find→Use Selection for Find) now works properly in
framesets in the documentation window.
•Key bindings can now be assigned to items in the User Scripts and
Window→Tools menus using the Key Bindings Preferences pane.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
