AppCode 2018.1 EAP: location simulation support and more

New AppCode 2018.1 EAP is available for download on our site.

Location simulation

This build brings AppCode the long-awaited support for location simulation. Open the Run Configurations dialog and select the location you need:Location settings
Change it on the fly using the Simulate Location button in the Run or Debug tool window:Change location

Create your custom location setup and use it in the same way as in Xcode:Custom location

Vertical font spacing: Xcode mode

In this build, we added an experimental feature which allows you to use the same vertical font spacing as found in Xcode. You can enable it via ⇧⌘ARegistry → turn on editor.text.xcode.vertical.spacing. Now you can use the same line spacing values as Xcode does in Preferences | Editor | Font | Line spacing and have the same vertical spacing for the specific font:

  • Tight Spacing = 1.0
  • Normal Spacing = 1.1:Normal spacing example
  • Relaxed Spacing = 1.2

Together with the improvements mentioned in this post, this option makes the font rendering in AppCode editor the same as in Xcode.

Other

Several important regressions are addressed in this build:

  • Problem with non-clickable links in the console window (OC-16709)
  • Forward declaration of classes is not recognized by AppCode (OC-16472)
  • False-negative errors shown for macros in Objective-C (OC-16799)

Besides, TSLint plugin is now bundled in AppCode.

The full release notes are available here.

Your AppCode team
JetBrains
The Drive to Develop

This entry was posted in Announcement and tagged , , . Bookmark the permalink.

9 Responses to AppCode 2018.1 EAP: location simulation support and more

  1. Rob Mayoff says:

    It appears to be editor.text.xcode.vertical.spacing, not xcode.editor.vertical.font.spacing.

  2. Pas says:

    To use default Xcode font in AppCode (SF Mono):

    https://simonfredsted.com/1438

    The colour schemes are not quite right. If you import the default scheme from Xcode, it shows, for example, the documentation comments as: #007400, but they should be #218401. Also, AppCode will show types in a different colour depending on whether they come from the same module or not. For example:

    var myVar: MyType!

    “MyType” will be coloured differently if in the current module. Also, “myVar” will be black above, but a shade of aqua when used later in the class. It would be nice if this were all totally consistent with Xcode.

    • Pas says:

      I mean that *Xcode* will show types in a different colour depending on whether they come from the same module or not.

    • Pas says:

      If there’s anyway in the .icls file to provide different colours for a variable definition versus a variable reference, please let me know! Thanks.

    • Stanislav Dombrovsky says:

      To use default Xcode font in AppCode (SF Mono):

      Any font available on macOS can be used this way and it’s clear. As I wrote, it’s prohibited to use SF Mono font in any application except Terminal and Xcode. To be more specific: there is a copyright note inside the font file that says the following:

      You may use the Apple Font solely in conjunction with Apple-branded applications, including, but not limited to, Xcode, Terminal.app and Console.app. You may not embed or use the Apple Font in or with any other software applications or programs or other products and you may not use the Apple Font to create, develop, display or otherwise distribute any content, documentation, artwork or any other work product.
      You may use the Apple Font only for the purposes described in this License or as otherwise expressly permitted by Apple in writing.

      It means that you cannot even share the screenshot with such font.

    • Stanislav Dombrovsky says:

      The colour schemes are not quite right. If you import the default scheme from Xcode, it shows, for example, the documentation comments as: #007400, but they should be #218401. Also, AppCode will show types in a different colour depending on whether they come from the same module or not.

      Please see my note about IDEA-185408 and IDEA-185409 in this post

  3. Pas says:

    I wrote a detailed response with some complaints about the Xcode theme. The response showed as awaiting moderation. When I came back to check the page, the response had been deleted. Not impressed, JetBrains.

Leave a Reply

Your email address will not be published. Required fields are marked *