Pixelmator for iOS Gains iPad Pro Optimization, Apple Pencil 2 Support

Discussion in 'iOS Blog Discussion' started by MacRumors, Feb 12, 2019.

  1. MacRumors macrumors bot

    MacRumors

    Joined:
    Apr 12, 2001
    #1
    [​IMG]


    The Pixelmator app for iOS devices received a major update today, adding support for Apple's newest iPad Pro models.

    The app's interface has been optimized for the 11 and 12.9-inch iPad Pros, and the double tap gesture introduced with the Apple Pencil 2 can now be used in Pixelmator.

    [​IMG]
    Pixelmator on 11-inch iPad Pro before update on left, after update on right​

    According to the release notes for the update, Pixelmator will respect the user's global settings for the double tap gesture, so if it's set to switch to the erase tool, for example, it will be set that way in Pixelmator as well.

    In addition to iPad Pro optimization, the new version of Pixelmator addresses several bugs, as outlined in the full release notes:
    Pixelmator for the iPad can be downloaded from the App Store for $4.99. [Direct Link]

    Article Link: Pixelmator for iOS Gains iPad Pro Optimization, Apple Pencil 2 Support
     
  2. ikir macrumors 65816

    ikir

    Joined:
    Sep 26, 2007
  3. berrymetal macrumors regular

    berrymetal

    Joined:
    Jul 25, 2017
  4. Scottsoapbox macrumors 6502a

    Scottsoapbox

    Joined:
    Oct 10, 2014
    #4
    It's looking like all the major apps will have optimized just in time for this year's iPad Pro 11.4". :cool:
     
  5. now i see it macrumors 68030

    Joined:
    Jan 2, 2002
    #5
    App details say it works with iOS 9.1 but it doesn't. Still hangs like it always has after the last update over a year ago.
    I tell them, but they don't care and won't change the system requirements on the app page. Weird.
     
  6. jonblatho macrumors 6502a

    jonblatho

    Joined:
    Jan 20, 2014
    Location:
    Oklahoma/Missouri
    #6
    Fixes for years-old OS releases are almost always at the very bottom of the pile and a common answer is just to bump the deployment target such that the app isn't supported on that OS release anymore to close the issue.

    Maybe a fix will come, but I wouldn't hold my breath.
     

Share This Page