Xcode 4.4 4F155i - tab key behavior
| Originator: | evan | ||
| Number: | rdar://11299308 | Date Originated: | 23-Apr-2012 09:36 AM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | 4F155i |
| Classification: | UI/Usability | Reproducible: | Always |
Summary: Xcode 4.4 adds in automatic closing syntax when a closing punctuation is typed. E.g. type `[` and automatically `]` is added after the insertion cursor. So far, I have discovered that you can use the normal "tab-to-autocomplete" that is familiar from Xcode code sense. However, if you have a method with unfilled arguments later in your code and try to tab-complete the closing syntax, the insertion cursor jumps to the field instead. Steps to Reproduce: 1. Type `NSDictionary *d = [NSDictionary dictionaryWithObj` 2. Choose the method "dictionaryWithObjects: forKeys:" from the code sense drop down 3. Think "oh, derp. I need to go make two arrays" 4. Back up a line and type `NSArray *objects = [NSArray arrayWithObjects:@"herp", @"derp", nil` 5. You are now at the end of what you want to type and you want to autocomplete the `]` that's on the other side of your insertion cursor - so hit the tab key 6. Insertion cursor jumps down to the `NSDictionary *d = [NSDictionary dictionaryWithObjects: forKeys:]` line Expected Results: After step 5, I expect to hit the tab key, have the closing syntax autocompleted for me so I can then type a semicolon and then tab AGAIN to get to the argument of the method I'm not done with. Actual Results: Regression: Notes: See attached annotated screen grab 23-Apr-2012 09:36 AM Evan DeLaney: 'Screen Shot 2012-04-23 at 9.27.20 AM.jpg' was successfully uploaded
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!