Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Yes, that is exactly what I am talking about. The concept of rasterizing an image seems, in my humble opinion, outdated. AD can definitely work with comps of multiple resolutions, imagine dropping in images and never worrying about working at highest res, because they always are at source resolution. Everything is best-res, and the pixel preview shows you the "flattened" preview. I find, it would be sick :) [edit:] I find, I also live in a dream lol
  2. I love AD, but some little annoyances have become really abrasive over time. Here is my list of things that really really get to me. After writing the list, I realize it could be read as an angry post, it is not. I am not *angry* or something, just annoyed :) AD is a great peice of software and I love it, I just wish it dealt better with the little details that affect workflow and work speed greatly (the repetitive stuff). All effects and dialogs start at 0. Why!? For example feathering, why not put a good default value like 1? Who uses feather at 0? Same goes for shadows/outlines/all effects. Why not start with a basic shadow, so we can see immediately if it fits the style? You have to triple click to select the full text of an edit box. A lot of time you don't triple click well enough. Why? There has been exactly 0 times in 1 year of usage that I've had to change a specific number, and 100% of times when I need to change it completely. Could you make the number boxes single-click select-all please? Dialogs don't auto select edit boxes. It would make workflow so much better. Apply thing > enter number > tab a few times > enter number > enter. Almost no wasted time selecting mouse. Your shortcut/input stack is a little broken, sending clicks after a spacebar-move and things like that. This is a bigger deal, but that portion of the backend should be redesigned/rethought imho. Placing an image, why do I have to rasterize it everytime? Why can't I just place an image and work? The layer creation assistant is a little funky. I do not know how or what exactly is the issue, so I'll just flag it as a sometimes annoying thing where you think you are drawing somewhere/something and your not. It is definitely useful many times. I have not yet put the finger on the use-cases that "breaks" it for me. Hope this is useful, lots of little simple things in there. Good day
  3. Please. No need to hide under an un-precise tool :(
  4. Affinity Designer is great, great I say! Exporting icons would be great too! XD
  5. I've read a thread about a full animation system which is way out-of-scope. But, a simple layer to frame animated gif export would be handy and quite welcomed. Also completely non-intrusive. Thank you
  6. Alright then, I'll report it to apple next time. Cheers
  7. Working on a 8x8 pixel image. Had 1 pixel layer. Transparent background. Save document > create folder > crashed. Process: Affinity Designer [4241] Path: /Applications/Affinity Designer.app/Contents/MacOS/Affinity Designer Identifier: com.seriflabs.affinitydesigner Version: 1.4.2 (1.4.3) App Item ID: 824171161 App External ID: 817630376 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Affinity Designer [4241] User ID: 501 Date/Time: 2016-07-20 12:38:10.753 -0400 OS Version: Mac OS X 10.11.6 (15G31) Report Version: 11 Anonymous UUID: EA4FD2C6-2B5A-3284-4AF1-FB06A5FE3302 Sleep/Wake UUID: 5CE29262-8553-4428-A660-1034607E7205 Time Awake Since Boot: 96000 seconds Time Since Wake: 4200 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: objc_msgSend() selector name: windowNumber Performing @selector(saveDocument:) from sender NSMenuItem 0x7fcd62594570 ViewBridge hint(s): ( "<NSLayerCentricRemoteView 0x7fcd67d89630> com.apple.appkit.xpc.openAndSavePanelService NSSavePanelService" ) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff9a7334d7 objc_msgSend + 23 1 com.apple.AppKit 0x00007fff879feae4 -[NSApplication _doModalLoop:peek:] + 751 2 com.apple.CoreFoundation 0x00007fff943b1a6c __invoking___ + 140 3 com.apple.CoreFoundation 0x00007fff943b18fe -[NSInvocation invoke] + 286 4 com.apple.ViewBridge 0x00007fff8639a30b withHintInProgress + 501 5 com.apple.ViewBridge 0x00007fff8639a091 __deferNSXPCInvocationOntoMainThread_block_invoke_2 + 220 6 com.apple.ViewBridge 0x00007fff86338b4f +[NSViewServiceApplication withHostPID:invoke:] + 46 7 com.apple.ViewBridge 0x00007fff86399f5f __deferNSXPCInvocationOntoMainThread_block_invoke + 129 8 com.apple.ViewBridge 0x00007fff86399b6a __deferBlockOntoMainThread_block_invoke_2 + 448 9 com.apple.CoreFoundation 0x00007fff943d54ac __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 10 com.apple.CoreFoundation 0x00007fff943b4d05 __CFRunLoopDoBlocks + 341 11 com.apple.CoreFoundation 0x00007fff943b4a6b __CFRunLoopRun + 2347 12 com.apple.CoreFoundation 0x00007fff943b3ed8 CFRunLoopRunSpecific + 296 13 com.apple.HIToolbox 0x00007fff8acd1935 RunCurrentEventLoopInMode + 235 14 com.apple.HIToolbox 0x00007fff8acd176f ReceiveNextEventCommon + 432 15 com.apple.HIToolbox 0x00007fff8acd15af _BlockUntilNextEventMatchingListInModeWithFilter + 71 16 com.apple.AppKit 0x00007fff8778fdf6 _DPSNextEvent + 1067 17 com.apple.AppKit 0x00007fff8778f226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 18 com.apple.AppKit 0x00007fff879fea82 -[NSApplication _doModalLoop:peek:] + 653 19 com.apple.AppKit 0x00007fff87bdf6fb __35-[NSApplication runModalForWindow:]_block_invoke + 126 20 com.apple.AppKit 0x00007fff879fc375 -[NSApplication runModalForWindow:] + 156 21 com.apple.AppKit 0x00007fff879fbe47 -[NSVBSavePanel runModal] + 229 22 com.seriflabs.libcocoaui 0x0000000107b76296 -[DocumentView saveAsDocument] + 326 23 com.seriflabs.libcocoaui 0x0000000107b75b15 -[DocumentView saveDocument] + 805 24 libsystem_trace.dylib 0x00007fff9b3cc07a _os_activity_initiate + 75 25 com.apple.AppKit 0x00007fff879f8dbd -[NSApplication sendAction:to:from:] + 460 26 com.apple.AppKit 0x00007fff879f8b57 -[NSMenuItem _corePerformAction] + 336 27 com.apple.AppKit 0x00007fff879f88b7 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114 28 libsystem_trace.dylib 0x00007fff9b3cc07a _os_activity_initiate + 75 29 com.apple.AppKit 0x00007fff879f77a5 -[NSMenu performKeyEquivalent:] + 357 30 com.seriflabs.libcocoaui 0x0000000107b0605f -[Application handleKeyDown:] + 767 31 com.seriflabs.libcocoaui 0x0000000107b05bfb -[Application sendEvent:] + 443 32 com.apple.AppKit 0x00007fff87783df2 -[NSApplication run] + 796 33 com.apple.AppKit 0x00007fff8774d368 NSApplicationMain + 1176 34 com.seriflabs.affinitydesigner 0x00000001068c30b4 0x1068c1000 + 8372
  8. The team has to sit down and design the greatest arrow tool ever. I don't expect anything less from them as the whole software proves they're capable. They just need to put some time aside for it. So please team managers, your current arrow tool is an insult, make some time for a new arrow tool Done Right TM
  9. Hello again, I know this is the weirdest, most "out-of-date-format" request, but I've been working with ppm a ton lately (mapping stuff). I only ask about these formats because they are ridiculously easy to support. Like, a few hours (maximum) to integrate. Considering OS X preview doesn't support them, it would add yet another selling point for affinity designer. I don't expect this to be high priority (if even considered), but maybe someday you have a few minutes to spare on this ^_^ Cheers! https://en.wikipedia.org/wiki/Netpbm_format
  10. Well I'm talking about the only way to make arrows right now (arrow object thing) ;) I wish AD becomes the BEST arrow software in existence, it's not like the team hasn't proven their talent and forward thinking in many other areas. So yes, +1 to arrow line tool (a-la Skitch). But also, arrow heads for paths. Making curved arrows is unconventionally tedious! Even Illustrator has overly complex and tedious arrows :( [edit:] So the roadmap mentions arrow heads, but not a rework of the arrow tool (arrow shape tool). This has to be rethought, the tool is painful.
  11. The current arrow tool is horrendous, nuff said :P My preferred tool for arrows is in Skitch (it is free on App Store). How they do it is: click (arrow begins) -> drag (form arrow) -> release click (arrow points here). It is super natural and fast. Also, every single path brush should have arrow heads. Thank you. Arrows a major pain point, but of course you guys rock and keep it up! :)
  12. Great! I'm glad you could reproduce it :) It definitely feels worst because the whole app is so snappy! hehe
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.