Re: That frustrating Refactor... command
Re: That frustrating Refactor... command
- Subject: Re: That frustrating Refactor... command
- From: Quincey Morris <email@hidden>
- Date: Thu, 17 Dec 2009 12:22:20 -0800
On Dec 17, 2009, at 11:44, Jens Alfke wrote:
> Xcode's Refactor feature is very useful. Unfortunately the contextual-menu command for it seems to enable and disable at random, and quite a lot of the time that I want to rename a class/ivar/method it remains stubbornly grayed-out, even though I've used it in the same circumstances earlier. (As an example, yesterday it let me rename two classes in a project, but not two others that were nearly identical. I have no idea why.)
>
> Is this a known bug, or are there just some deep subtleties to when refactoring will or won't work? If the latter, it would be really nice if instead of disabling the command, Xcode would put up an alert explaining why it couldn't refactor.
It remains mysterious why this happens, and because it's a transient thing it's not even possible to capture the state for a bug report, AFAIK.
Based on a particularly egregious example (not of it being grayed out but of it producing an error message that wouldn't go away), I *believe* that what's happening is an inconsistency in the codesense index (or whatever it uses) where the current version of the method definition is correctly indexed, but a previous (and no longer existing) definition is also indexed and that causes Refactor to throw up in its hands in horror.
But that's pure speculation ...
_______________________________________________
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