davekeck / xcode-4-fixins Goto Github PK

How about if if the HideDistractions hot key toggled between hidden/standard view. How do you get back to "distracted state" easily?

Thanks for these great tweaks!

The Current Line Highlighter plugin doesn't seem to work for me on ML with Xcode 4.4. Anyone else have this problem?

Currently the FindFix only seems to apply to the Editor's find modal. It would also make sense to incorporate it into the Search Navigator.

If I open another assisant right of my code, then press Cmd+F, then Cmd+Enter to hide it again, the layout gets screwed up (you get a big grey box next to the code).

After a while more layout get screwed up. At some point, of the search bar were only 3 gradients visible, no controls whatsoever.

Great ideas here. So happy to have animations disabled - most of them perform so badly that I can't understand why they're there.

Something I'd love to see is ctrl-p and ctrl-n act as up and down arrows when browsing & filtering the symbol list. This works as expected in every other list in OS X, and in most places in Xcode - I can't understand why it doesn't work there. Drives me nuts to have to reach for the up/down keys for that one thing.

Any ideas on how this could be hacked in?

See title.

Xcode limitation? Workaround?

Is this cause the API is closed or because its all "a-swizzle"?

I filed a rdar on this long ago but have not seen anything done with it. Hopefully you can fix it. In the theme color editor under console you can change the Instruction Pointer color. This is the color of the line when the debugger stops on it.

Even though the panel allows you to set an alpha, it is not respected in the view. This means that for people with dark background themes and medium to dark text, the code is not very legible underneath the color.

Can you help?

I couldnt find anywhere that LOG_XXX or DEBUG_XXX was #define'd, etc....

commenting out the NSlog's is dicey in places...

a preprocessor Macro, or something, pretty please?

xcodebuild environment gets bombarded with this kind of stuff...

2012-08-28 09:46:51.316 xcodebuild[1369:1207] XCFixin_FindFix initialization attempt 2/3... 2012-08-28 09:46:51.317 xcodebuild[1369:1207] XCFixin_FindFix initialization successful! 2012-08-28 09:46:51.320 xcodebuild[1369:1207] XCFixin_DisableWriteStateData initialization attempt 2/3... 2012-08-28 09:46:51.320 xcodebuild[1369:1207] Assertion failed (file: /Volumes/+10RAID2000/ServiceData/git/Xcode-4-Fixins/XCFixin_DisableWriteStateData/../Shared Code/XCFixin.m, function: IMP XCFixinOverrideMethod(Class, SEL, IMP), line: 11): class 2012-08-28 09:46:51.321 xcodebuild[1369:1207] Assertion failed (file: /Volumes/+10RAID2000/ServiceData/git/Xcode-4-Fixins/XCFixin_DisableWriteStateData/XCFixin_DisableWriteStateData.m, function: +[XCFixin_DisableWriteStateData pluginDidLoad:], line: 25): gOriginalWriteStateData 2012-08-28 09:46:51.322 xcodebuild[1369:1207] XCFixin_DisableWriteStateData initialization failed.

Please add auto population of the search field with the current word at the caret (if there's any), just like Visual Studio does. This avoids this annoying select->copy->find->paste sequence. Thank you.

I'd like to be able to alphabetize my @properties with one click, rather than doing it by hand. Similar to Structure->Re-Indent. Is this possible?

I'd be interested in creating this myself if you could point me in the right direction.

Hey guys, as the project grows I think the workspace approach to installing the plugins makes less and less sense, so I just deleted the workspace and moved the plugin directories into the root directory. My reasoning is that once we have > 10 plugins, Xcode's behavior will change significantly after installing the entire plugin collection which might not be what users want. Let me know if you all disagree and we can bring the workspace back.

Reproduction steps:

1. Install XCFixin_FindFix.xcplugin
2. Open Xcode 5
3. Press Command - F, or Command - Option - F

Xcode crashes.

Version: 5.0 (3330.25)
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Sending hideDistractions: to XCFixin_HideDistractions from <NSMenuItem: 0x6180002a1380 Hide Distractions>
UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[_NSViewLayoutAux menu]: unrecognized selector sent to instance 0x6180002a1da0
....

6 0x00007fff8f6f3617 -[NSMenu insertItem:atIndex:] (in AppKit)
7 0x0000000114a7f04c +[XCFixin_HideDistractions hideDistractions:] at /Users/localadmin/Library/Application Support/Alcatraz/Plug-ins/XCFixin_HideDistractions/XCFixin_HideDistractions/XCFixin_HideDistractions.m:103 (in XCFixin_HideDistractions)
8 0x00007fff8f912f40 -[NSApplication sendAction:to:from:] (in AppKit)
9 0x000000010b9bfc89 __37-[DVTApplication sendAction:to:from:]_block_invoke (in DVTKit)
10 0x000000010b2df1d1 DVTInvokeWithFailureHint (in DVTFoundation)
11 0x000000010b7f1810 -[DVTApplication sendAction:to:from:] (in DVTKit)
12 0x00007fff8f92e108 -[NSMenuItem _corePerformAction] (in AppKit)
13 0x00007fff8f92de44 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] (in AppKit)
14 0x00007fff8f92cfbc -[NSMenu performKeyEquivalent:] (in AppKit)
15 0x00007fff8f929801 -[NSApplication _handleKeyEquivalent:] (in AppKit)
16 0x00007fff8f898944 -[NSApplication sendEvent:] (in AppKit)
17 0x000000010c350c5b -[IDEApplication sendEvent:] (in IDEKit)

Console reports:
Reason for Failure: *** -[NSArrayM insertObject:atIndex:]: object cannot be nil.

Any ideas on this one?

The thing I want most in Xcode is to turn off the damned idiotic animations when opening/closing the nav/info panels and when expanding/collapsing the project folder content.

Thanks for putting this together.

At the risk of asking a stupid question... should the Xcode 4 fixins continue to support Xcode 4? :)

I've been fixing up the fixins for 5.1. Xcode 5.1 complained about the GC support, so I let it convert everything to ARC. Seems to work fine for 5.1 (I'll push the WIP branch to github in the next day or two) - but now none of them load into Xcode 4.6.2. Xcode prints a GC capability mismatch error to the console for each one.

It's annoying how quick Apple is to drop things. But since they seem to have switched to giving upgrades out for free, for OS X, Xcode, and iOS - and anybody coding for iOS is automatically committed to the Xcode treadmill - I imagine virtually everybody will upgrade.

So is continued Xcode 4 support felt to be important?

Any comments?

--Tom