Jump to content
You must now use your email address to sign in [click for more info] ×

dangerman2000

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by dangerman2000

  1. I got this error as well. I had used the same name twice for a slice and it gave the error. It was a bit misleading. It was hard to track down because there were a plethora of icons on the page that I was exporting (scrolling on the small 'Slices' panel). Expected: There should be validation when naming the slice to ensure it's a unique name. I have not checked to see if it checks for valid names (avoid invalid characters : ' " etc.) , but if not it should do that too! :)
  2. Currently there is a checkbox to export images @1x and @2x... which is superb and super helpful. With iPhone 6, we now need to export @3x as well. This feature request is to include a checkbox for @3x next to the @2x checkbox to make exporting assets easy. See article: https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iOS8.html (excerpt) Supporting New Screen Scales The iPhone 6 Plus uses a new Retina HD display with a very high DPI screen. To support this resolution, iPhone 6 Plus creates a UIScreen object with a screen size of 414 x 736 points and a screen scale of 3.0 (1242 x 2208 pixels). After the contents of the screen are rendered, UIKit samples this content down to fit the actual screen dimensions of 1080 x 1920. To support this rendering behavior, include new artwork designed for the new 3x screen scale. In Xcode 6, asset catalogs can include images at 1x, 2x, and 3x sizes; simply add the new image assets and iOS will choose the correct assets when running on an iPhone 6 Plus. The image loading behavior in iOS also recognizes an @3x suffix. (/excerpt)
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.