Xcode: Jump to Definition Chooses Implementation in Different Target
| Originator: | paul | ||
| Number: | rdar://16383799 | Date Originated: | 3/20/14 |
| Status: | Open | Resolved: | |
| Product: | Xcode | Product Version: | Version 5.1 (5B130a) |
| Classification: | UI/Usability | Reproducible: | Sometimes |
Summary: Command clicking or option-clicking-then-selecting-jump-to-definition on a method signature or selector jumps to an implementation in another target, not the desired implementation. Steps to Reproduce: 1. Create an Xcode project with a class in it, with at least two methods. Have method1 call method2, so you can jump to definition within the implementation file. 2. Create a new target, and create a new implementation (.m) of that class. 3. Jump to the definition of method2 from method1 from the first target. Expected Results: Jumping to the definition of method2 from method1 should jump to method2's implementation in target1, or at least provide a list of available targets to choose from. Actual Results: Most of the time, jumping to the definition of method2 from method1 in target 1 jumps to method 2's definition in target 2.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!