Jump to content

n8o

Members
  • Content count

    24
  • Joined

  • Last visited

About n8o

  • Rank
    Newbie

Contact Methods

  • Website URL
    http://amuses.me/

Profile Information

  • Gender
    Not Telling
  • Location
    Saskatchewan, Canada
  • Interests
    iPhone app & dame design; physics; dadding.
  1. I like all the changes so far, and the rate that they're coming, so don't take my constant commenting in this thread the wrong way :P I'm just a broken record. But I love Affinity. Just a broken record. But I love Affinity ;)
  2. The new pixel snapping feature is nice! However, it still seems to override all other snapping. Guides are basically useless as it will snap to any and all pixels regardless of nearby guides. There needs to be priorities for snapping, and guides et all need to trump the pixel snapping (or some mixed variation, such as guide snapping is still "strong" but the final result is rounded to nearest pixel). Adobe has this very solid ATM and it may be worth analyzing their methods.
  3. Any chance you could make this a setting?
  4. SVGs I export to use in PaintCode (iOS vector graphics app) don't appear once imported. After talking to the developer, the problem is that the SVG viewport width and height both defined as 100%. Paintcode expects pixel/point sizes. The Paintcode developer will improve their handling of these kinds of viewports, but it seems to me that Designer should possibly specify a viewport equal to the document size.
  5. I am VERY excited to hear this. Downloading immediately!
  6. Actually, I think you're right: I managed to change my default settings :( The size is maintained, and I would *expect* it to revert to bounds, but I do see there's a button to do that.
  7. If I create a slice from a layer and then delete that slice, I would expect it to truly forget the slice. Instead, as soon as I create a new slice from that layer it maintains the shape and settings it had previously. These even persist to duplicates, which is unexpected.
  8. n8o

    Copy merged

    Just wanted to add my +1 as well. I need this for testing mockups on device especially. Apps like Skala Preview will send any screen-sized image on the clipboard to a connected device for preview. Pretty critical for checking iPhone/iPad designs! fwiw Sketch has the preview functionality built-in, but I don't think that's necessary if copy merged is working.
  9. Hi, The current iPhone 6 template is 326 dpi. This is the physical resolution of the device, but not the size of the device from the development side. When creating apps the dpi for iOS is always 144 (when retina). The current template's ppi is problematic when creating mocks and specifying type sizes. Everything would be too big. I have attached an example image to illustrate the differences. As you can see, when type is specified in Xcode itself it matches the 144 ppi image from Affinity.
  10. MEB, Thanks for the response. I came here as a long-time Xara user that switched to Mac. Previously, OS X has had nothing with the depth of features (especially speed) of Xara. Lots of longtime Xara users have been saying that Affinity has finally done it, and after playing for just an hour that's clearly correct. Affinity has the foundation necessary, and it's certainly an impressive 1.0 release. My issue is whether I can use it for my day-to-day work, where I need a rock-solid tool to crank out graphics for screen. Pixel snapping is clearly a necessity. I really hope this is improved in a 1.x update, but for now I've continued my trial with a bit of a hack: I set the dpi to 144px (without using the retina checkbox) with pixel units, but set snapping to points, which are now 2px big. That seems to be effectively giving me single pixel snapping since Affinity prefers half-point snapping :P So, I'll keep playing. Please keep up the good work.
  11. Half pixel snapping is entirely useless. The only reason I created an account on this forum was to mention how broken it is to have any sub-pixel snapping. Honestly, I think this ends my 10-day trial; doing design for screens/mobile requires pixel-perfect edges which are completely ruined by anti-aliasing on .5 pixel positions. I'm trying to be nice here, but even just reading that the fix is only under "consideration" is disheartening. It may be that Affinity is not meant for screen designers?
×