Jump to content

Achim63

Members
  • Content Count

    97
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Achim63 reacted to toyotadesigner in [Duplicate] Affinity Photo without memory!   
    It is so disappointing, that Photo still does NOT remember the original folder where I opened the file (TIFF) when exporting it after working on it!
     
    I have to pull up XnView MP every time from the background to check the path, then return to Photo, walk through the file system to save/export the file.
     
    Working with lots of very large files in different folders on my external hard drives every day, this causes too many breaks and a giant delay for me. All the hassle just because Photo can not remember the path...
     
    Is it really too much what I require for a smooth workflow? Any other software I am using on my Mac does this automatically, so why not Affinity?
     
    Instead of adding funky and kinky gimmicks, could somebody please work on this issue?
     
    Too bad, but until this braindead behavior will be solved, I'll stick with Photoline (another blazingly fast 16 bit image editor)
  2. Like
    Achim63 got a reaction from ZeeArts in Crash trying to open preferences in AP 1.6.6   
    First of all, thanks a lot for the update! I tried the light GUI in AD and it's much easier on my eyes than the dark theme.
     
    On both my iMacs (an older one at work, a new Retina one at home, both on macOS 10.13.1, German), AP crashes as soon as I try to open the preferences (from the menu or with Cmd+,).
    I tried deleting the user .plist to no avail.
     
    Here's the relevant part of the crashlog:
     
    Process:               Affinity Photo [4211]
    Path:                  /Applications/Affinity Photo.app/Contents/MacOS/Affinity Photo
    Identifier:            Affinity Photo
    Version:               1.6.6 (1.6.6)
    App Item ID:           824183456
    App External ID:       824080612
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Affinity Photo [4211]
    User ID:               502
    Date/Time:             2017-11-02 16:38:49.625 +0100
    OS Version:            Mac OS X 10.13.1 (17B48)
    Report Version:        12
    Anonymous UUID:        0323F9B2-201F-275E-6096-238AE356C7D4
    Sleep/Wake UUID:       84798B34-6573-4739-B888-B52D424F4C2D
    Time Awake Since Boot: 36000 seconds
    Time Since Wake:       19000 seconds
    System Integrity Protection: enabled
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
    Exception Codes:       0x0000000000000001, 0x0000000000000000
    Exception Note:        EXC_CORPSE_NOTIFY
    Termination Signal:    Illegal instruction: 4
    Termination Reason:    Namespace SIGNAL, Code 0x4
    Terminating Process:   exc handler [0]
    Application Specific Information:
    Crashing on exception: NSConcreteAttributedString initWithString:: nil value
    Application Specific Backtrace 1:
    0   CoreFoundation                      0x00007fff4179953b __exceptionPreprocess + 171
    1   libobjc.A.dylib                     0x00007fff681a8942 objc_exception_throw + 48
    2   CoreFoundation                      0x00007fff418297e5 +[NSException raise:format:] + 197
    3   Foundation                          0x00007fff43801c27 -[NSConcreteAttributedString initWithString:] + 135
    4   Foundation                          0x00007fff4380b4b4 -[NSConcreteAttributedString initWithString:attributes:] + 27
    5   libcocoaui                          0x00000001025f1a5f -[PreferenceController tableView:objectValueForTableColumn:row:] + 2239
    6   AppKit                              0x00007fff3eeb3bfb -[NSTableView _dataSourceValueForColumn:row:] + 202
    7   AppKit                              0x00007fff3ef6c591 -[NSTableView preparedCellAtColumn:row:] + 471
    8   AppKit                              0x00007fff3ef6c21f -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 50
    9   AppKit                              0x00007fff3ef6bf2a -[NSTableView drawRow:clipRect:] + 2186
    10  AppKit                              0x00007fff3ef6b3a0 -[NSTableView drawRowIndexes:clipRect:] + 527
    11  AppKit                              0x00007fff3ee89be0 -[NSTableView drawRect:] + 1522
    12  AppKit                              0x00007fff3f5d3e3d _NSViewDrawRect + 83
    13  AppKit                              0x00007fff3f5e10d4 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:shouldChangeFontReferenceColor:] + 1578
    14  AppKit                              0x00007fff3f5e0aa4 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inContext:shouldChangeFontReferenceColor:] + 56
    15  AppKit                              0x00007fff3ee73374 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 289
    16  AppKit                              0x00007fff3ee72f08 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 1577
    17  AppKit                              0x00007fff3ee728d9 -[NSView(NSLayerKitGlue) drawLayer:inContext:] + 77
    18  QuartzCore                          0x00007fff4c81d6dd CABackingStoreUpdate_ + 279
    19  QuartzCore                          0x00007fff4c81d5bc ___ZN2CA5Layer8display_Ev_block_invoke + 54
    20  QuartzCore                          0x00007fff4c81cd9f -[CALayer _display] + 1824
    21  AppKit                              0x00007fff3ee7189e _NSBackingLayerDisplay + 556
    22  AppKit                              0x00007fff3ee66715 -[_NSViewBackingLayer display] + 242
    23  QuartzCore                          0x00007fff4c80ea61 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 633
    24  QuartzCore                          0x00007fff4c80e50f _ZN2CA5Layer28layout_and_display_if_neededEPNS_11TransactionE + 35
    25  QuartzCore                          0x00007fff4c80d641 _ZN2CA7Context18commit_transactionEPNS_11TransactionE + 319
    26  QuartzCore                          0x00007fff4c80d1f5 _ZN2CA11Transaction6commitEv + 487
    27  AppKit                              0x00007fff3f61c6e4 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 283
    28  CoreFoundation                      0x00007fff417324d7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
    29  CoreFoundation                      0x00007fff417323ff __CFRunLoopDoObservers + 511
    30  CoreFoundation                      0x00007fff41714f08 __CFRunLoopRun + 1240
    31  CoreFoundation                      0x00007fff41714797 CFRunLoopRunSpecific + 487
    32  HIToolbox                           0x00007fff40a29866 RunCurrentEventLoopInMode + 286
    33  HIToolbox                           0x00007fff40a294df ReceiveNextEventCommon + 366
    34  HIToolbox                           0x00007fff40a29354 _BlockUntilNextEventMatchingListInModeWithFilter + 64
    35  AppKit                              0x00007fff3ed26a23 _DPSNextEvent + 2085
    36  AppKit                              0x00007fff3f4bbe6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
    37  AppKit                              0x00007fff3ed1b831 -[NSApplication run] + 764
    38  AppKit                              0x00007fff3ecea9d2 NSApplicationMain + 804
    39  Affinity Photo                      0x00000001007acf54 Affinity Photo + 8020
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.AppKit                  0x00007fff3f051520 -[NSApplication _crashOnException:] + 109
    1   com.apple.AppKit                  0x00007fff3f61c923 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 858
    2   com.apple.CoreFoundation          0x00007fff417324d7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
    3   com.apple.CoreFoundation          0x00007fff417323ff __CFRunLoopDoObservers + 511
    4   com.apple.CoreFoundation          0x00007fff41714f08 __CFRunLoopRun + 1240
    5   com.apple.CoreFoundation          0x00007fff41714797 CFRunLoopRunSpecific + 487
    6   com.apple.HIToolbox               0x00007fff40a29866 RunCurrentEventLoopInMode + 286
    7   com.apple.HIToolbox               0x00007fff40a294df ReceiveNextEventCommon + 366
    8   com.apple.HIToolbox               0x00007fff40a29354 _BlockUntilNextEventMatchingListInModeWithFilter + 64
    9   com.apple.AppKit                  0x00007fff3ed26a23 _DPSNextEvent + 2085
    10  com.apple.AppKit                  0x00007fff3f4bbe6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
    11  com.apple.AppKit                  0x00007fff3ed1b831 -[NSApplication run] + 764
    12  com.apple.AppKit                  0x00007fff3ecea9d2 NSApplicationMain + 804
    13  com.seriflabs.affinityphoto       0x00000001007acf54 0x1007ab000 + 8020
     
  3. Like
    Achim63 got a reaction from arelenas in Crash trying to open preferences in AP 1.6.6   
    First of all, thanks a lot for the update! I tried the light GUI in AD and it's much easier on my eyes than the dark theme.
     
    On both my iMacs (an older one at work, a new Retina one at home, both on macOS 10.13.1, German), AP crashes as soon as I try to open the preferences (from the menu or with Cmd+,).
    I tried deleting the user .plist to no avail.
     
    Here's the relevant part of the crashlog:
     
    Process:               Affinity Photo [4211]
    Path:                  /Applications/Affinity Photo.app/Contents/MacOS/Affinity Photo
    Identifier:            Affinity Photo
    Version:               1.6.6 (1.6.6)
    App Item ID:           824183456
    App External ID:       824080612
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Affinity Photo [4211]
    User ID:               502
    Date/Time:             2017-11-02 16:38:49.625 +0100
    OS Version:            Mac OS X 10.13.1 (17B48)
    Report Version:        12
    Anonymous UUID:        0323F9B2-201F-275E-6096-238AE356C7D4
    Sleep/Wake UUID:       84798B34-6573-4739-B888-B52D424F4C2D
    Time Awake Since Boot: 36000 seconds
    Time Since Wake:       19000 seconds
    System Integrity Protection: enabled
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
    Exception Codes:       0x0000000000000001, 0x0000000000000000
    Exception Note:        EXC_CORPSE_NOTIFY
    Termination Signal:    Illegal instruction: 4
    Termination Reason:    Namespace SIGNAL, Code 0x4
    Terminating Process:   exc handler [0]
    Application Specific Information:
    Crashing on exception: NSConcreteAttributedString initWithString:: nil value
    Application Specific Backtrace 1:
    0   CoreFoundation                      0x00007fff4179953b __exceptionPreprocess + 171
    1   libobjc.A.dylib                     0x00007fff681a8942 objc_exception_throw + 48
    2   CoreFoundation                      0x00007fff418297e5 +[NSException raise:format:] + 197
    3   Foundation                          0x00007fff43801c27 -[NSConcreteAttributedString initWithString:] + 135
    4   Foundation                          0x00007fff4380b4b4 -[NSConcreteAttributedString initWithString:attributes:] + 27
    5   libcocoaui                          0x00000001025f1a5f -[PreferenceController tableView:objectValueForTableColumn:row:] + 2239
    6   AppKit                              0x00007fff3eeb3bfb -[NSTableView _dataSourceValueForColumn:row:] + 202
    7   AppKit                              0x00007fff3ef6c591 -[NSTableView preparedCellAtColumn:row:] + 471
    8   AppKit                              0x00007fff3ef6c21f -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 50
    9   AppKit                              0x00007fff3ef6bf2a -[NSTableView drawRow:clipRect:] + 2186
    10  AppKit                              0x00007fff3ef6b3a0 -[NSTableView drawRowIndexes:clipRect:] + 527
    11  AppKit                              0x00007fff3ee89be0 -[NSTableView drawRect:] + 1522
    12  AppKit                              0x00007fff3f5d3e3d _NSViewDrawRect + 83
    13  AppKit                              0x00007fff3f5e10d4 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:shouldChangeFontReferenceColor:] + 1578
    14  AppKit                              0x00007fff3f5e0aa4 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inContext:shouldChangeFontReferenceColor:] + 56
    15  AppKit                              0x00007fff3ee73374 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 289
    16  AppKit                              0x00007fff3ee72f08 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 1577
    17  AppKit                              0x00007fff3ee728d9 -[NSView(NSLayerKitGlue) drawLayer:inContext:] + 77
    18  QuartzCore                          0x00007fff4c81d6dd CABackingStoreUpdate_ + 279
    19  QuartzCore                          0x00007fff4c81d5bc ___ZN2CA5Layer8display_Ev_block_invoke + 54
    20  QuartzCore                          0x00007fff4c81cd9f -[CALayer _display] + 1824
    21  AppKit                              0x00007fff3ee7189e _NSBackingLayerDisplay + 556
    22  AppKit                              0x00007fff3ee66715 -[_NSViewBackingLayer display] + 242
    23  QuartzCore                          0x00007fff4c80ea61 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 633
    24  QuartzCore                          0x00007fff4c80e50f _ZN2CA5Layer28layout_and_display_if_neededEPNS_11TransactionE + 35
    25  QuartzCore                          0x00007fff4c80d641 _ZN2CA7Context18commit_transactionEPNS_11TransactionE + 319
    26  QuartzCore                          0x00007fff4c80d1f5 _ZN2CA11Transaction6commitEv + 487
    27  AppKit                              0x00007fff3f61c6e4 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 283
    28  CoreFoundation                      0x00007fff417324d7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
    29  CoreFoundation                      0x00007fff417323ff __CFRunLoopDoObservers + 511
    30  CoreFoundation                      0x00007fff41714f08 __CFRunLoopRun + 1240
    31  CoreFoundation                      0x00007fff41714797 CFRunLoopRunSpecific + 487
    32  HIToolbox                           0x00007fff40a29866 RunCurrentEventLoopInMode + 286
    33  HIToolbox                           0x00007fff40a294df ReceiveNextEventCommon + 366
    34  HIToolbox                           0x00007fff40a29354 _BlockUntilNextEventMatchingListInModeWithFilter + 64
    35  AppKit                              0x00007fff3ed26a23 _DPSNextEvent + 2085
    36  AppKit                              0x00007fff3f4bbe6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
    37  AppKit                              0x00007fff3ed1b831 -[NSApplication run] + 764
    38  AppKit                              0x00007fff3ecea9d2 NSApplicationMain + 804
    39  Affinity Photo                      0x00000001007acf54 Affinity Photo + 8020
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.AppKit                  0x00007fff3f051520 -[NSApplication _crashOnException:] + 109
    1   com.apple.AppKit                  0x00007fff3f61c923 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 858
    2   com.apple.CoreFoundation          0x00007fff417324d7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
    3   com.apple.CoreFoundation          0x00007fff417323ff __CFRunLoopDoObservers + 511
    4   com.apple.CoreFoundation          0x00007fff41714f08 __CFRunLoopRun + 1240
    5   com.apple.CoreFoundation          0x00007fff41714797 CFRunLoopRunSpecific + 487
    6   com.apple.HIToolbox               0x00007fff40a29866 RunCurrentEventLoopInMode + 286
    7   com.apple.HIToolbox               0x00007fff40a294df ReceiveNextEventCommon + 366
    8   com.apple.HIToolbox               0x00007fff40a29354 _BlockUntilNextEventMatchingListInModeWithFilter + 64
    9   com.apple.AppKit                  0x00007fff3ed26a23 _DPSNextEvent + 2085
    10  com.apple.AppKit                  0x00007fff3f4bbe6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
    11  com.apple.AppKit                  0x00007fff3ed1b831 -[NSApplication run] + 764
    12  com.apple.AppKit                  0x00007fff3ecea9d2 NSApplicationMain + 804
    13  com.seriflabs.affinityphoto       0x00000001007acf54 0x1007ab000 + 8020
     
  4. Like
    Achim63 reacted to LilleG in The 500th thread about GUI …   
    If you have perfect vision, or even very good vision, then you have no means of determining how "bad" it is for those of us with older less-effective vision.  I, for one, cannot tell which of the tools in the first post is the active one and I've made all the adjustments in Preferences that we are allowed to make to compensate.  
     
    And like Ronnyb, I don't understand why Affinity is so reluctant to accommodate us by offering the option of a light or dark UI.  We can't change our vision; they can, if they are willing, offer us something we desperately need.  
  5. Like
    Achim63 got a reaction from LilleG in The 500th thread about GUI …   
    I agree wholeheartedly - dark grey on a little bit less dark grey makes it really difficult to see selections. Some more contrast would do the GUI good. Or drawing a white (rounded) rectangle around the selected tool.
  6. Like
    Achim63 reacted to chrisA in Document Units   
    First thing: If you select New Document - Photo all sizes are in Inches. Nothing else. You only have a choice for "Print" documents.
     
    Why do you offer to change the units after selecting the document, when you expect that the user will work with the units of the preset? This is inconsistent.
     
    Even if I have to work with a format, which was originally defined in inches, I would prefer to with metric units, because I think this way. And my real world tools are that way. I don't want to use a calculator to get from my understanding of the world to something the program forces me to use.
     
    BTW. There were satellites lost, because some people still don't use metric units.
  7. Like
    Achim63 got a reaction from peter in The 500th thread about GUI …   
    I agree wholeheartedly - dark grey on a little bit less dark grey makes it really difficult to see selections. Some more contrast would do the GUI good. Or drawing a white (rounded) rectangle around the selected tool.
  8. Like
    Achim63 got a reaction from HolgerL in Pre-Development on opening - please fix this!   
    I'd guess that 95% of the users would prefer the pre-development we see in AP, not the blown out areas we see on the right in your photo. ETTR is a niche most people don't care too much about - not even "real" photographers (whoever that might be). As long as nothing is lost by the edits and it's possible to revert them I think it's a good thing to make some auto-adjustments. Take e.g. Lightroom - it usually adds lots of exposure to my RAWs, so they look overexposed and I usually have to take some of it back if I don't want whitish pastel colours.
    In all the examples in this forum where people complained about the development in AP, I would have preferred the AP photo as a starting point for further tweaking and not those from Lightroom, Capture One etc.. This is of course rather subjective and a matter of taste - and partly also a matter of monitor calibration (mine is calibrated with a Spyder4 Pro).
  9. Like
    Achim63 got a reaction from jojje in Import RAW from Photos   
    To find your RAW images, do a right click on your Photo library file (usually located in ~/Pictures/), select "Show package contents". In there there's a "Masters" folder which contains the JPG and RAW files next to each other in the subfolders which are ordered by date.
  10. Like
    Achim63 reacted to colbatzk in UI labels hard to read   
    Independent of factors such as age and eyesight, it is my perspective that a user interface should be optimized for readability and ease of usage. White or (worse) grey letters or pictograms on a dark/black background do not fulfill this request. Not even colorful pictograms do.
     
    As a user one should have at least the possibility to select which user interface suits her/him best. The reduction of the UI Gamma is no sufficient or satisfying "solution".
     
    Therefore, I ask the developers at Affinity, please come up  with a UI which is directed at readability. Thanks!
  11. Like
    Achim63 reacted to catlover in UI labels hard to read   
    I totally agree with the above posts.
    I for one, am an oldy (70+) and of course my eyesight is not what it used to be.
     
    I realize that in this industry the target consumers are the young ones, but hey, there are a lot of older people out there using computers nowadays.
     
    And I presume that the development of this suite of programs is not just done for a short number of years only.
    With  that in mind, it might be an idea to keep the future customers (and who will be, by that time, long term users) in mind as well.
     
    So, pretty please, developers, jack up the contrast settings in preferences.
  12. Like
    Achim63 reacted to keithrt in UI labels hard to read   
    One thing I've noticed while using Affinity Photo is despite using two 27" monitors, I find myself leaning in and squinting to read labels on tabs, particularly dimmed labels on inactive tabs. This might be alleviated somewhat by going to an 18% grey background instead of black and increasing the font size slightly. My eyesight close-in is still very good, but the constant squinting makes the interface uncomfortable to use.
  13. Like
    Achim63 got a reaction from anon1 in Vectorize pixel graphics   
    A feature that works awesome in Silhouette Studio (cutting plotter software, get it here for free: http://www.silhouetteamerica.com/software/silhouette-studio/) - take some drawing and make paths from it. It's just a few steps to get really good results: select a part of the image, then adjust high and/or low pass filters, threshold and scaling to your liking.
    I attached some pictures from that program to show the process involved. Notice the few anchors and nice curves that can be produced even with the rather low resolution jpg that I used.
     
    I use the Designer edition of Silhouette Studio which can import SVG, so I can switch to it for the features missing in AD - but it would be great to have it in AD directly, since Silhouette cannot export SVG.
     
    And while I'm at it: scanning directly in AD, so you can have a complete workflow inside AD after making a sketch with "real" media (something that Silhouette also can do).
     



  14. Like
    Achim63 got a reaction from billtils in Pre-Development on opening - please fix this!   
    I'd guess that 95% of the users would prefer the pre-development we see in AP, not the blown out areas we see on the right in your photo. ETTR is a niche most people don't care too much about - not even "real" photographers (whoever that might be). As long as nothing is lost by the edits and it's possible to revert them I think it's a good thing to make some auto-adjustments. Take e.g. Lightroom - it usually adds lots of exposure to my RAWs, so they look overexposed and I usually have to take some of it back if I don't want whitish pastel colours.
    In all the examples in this forum where people complained about the development in AP, I would have preferred the AP photo as a starting point for further tweaking and not those from Lightroom, Capture One etc.. This is of course rather subjective and a matter of taste - and partly also a matter of monitor calibration (mine is calibrated with a Spyder4 Pro).
  15. Like
    Achim63 reacted to Petar Petrenko in Affinity is NOT Adobe!   
    It is absolutelly wrong. No one designer uses only one kind of app. Everyone needs something from all these 3 apps. And so it will be absolute need for only one app that will merge all the three of them. It is very irritating to jump from one to another app just to do a portion of the job and then to continue to the third one, and so on.
    I completelly agree with Achim63, and I have posted this same question a month or two, ago.
  16. Like
    Achim63 got a reaction from Petar Petrenko in Affinity is NOT Adobe!   
    That's how Adobe does it - why should that be the best approach? The three have much code in common - e.g. the prepress and printing capabilities are a necessity for all of them, as are typography features. So what I'm thinking of is more of a publishing framework, where you can switch to the specialized part whenever needed. Remember the OpenDoc philosophy Apple introduced years ago? It resembles the personae approach we see in AD. So I really don't see the necessity to have three programs when the transitions between them are so fluent.
  17. Like
    Achim63 got a reaction from Petar Petrenko in Affinity is NOT Adobe!   
    Unfortunately Affinity is already doing the same - instead of putting the Liquify and Development personae into AD, they made it AP, so you'll have a second app to pay for. I'd rather pay twice the price for AD and have it all in one package.
    What will be next? Maybe an Affinity Painter app - instead of giving us custom brushes and full Wacom support in AD with a "natural media" persona, they might put it in even one more extra package. I hope I'm not giving them ideas here ...
    But maybe the planned layout app will make my wish come true and include all personae under one roof - they could even make the different personae available as in-app purchases, so they'll be kind of "plug-ins".
  18. Like
    Achim63 got a reaction from wehpet in We need a German Forum here!   
    No, please don't. Then we'd need Spanish and French and Japanese and Russian etc. as well - and the developers would maybe miss important issues.
    How about opening your own German Affinity blog or something similar if you want to discuss the apps in German?
     
    Everybody should have at least basic knowledge of English by now, it's taught in school and you wont get far in any job without it anyways. It's such an easy language to learn (I find e.g. Spanish much more demanding regarding grammar and vocabulary).
  19. Like
    Achim63 reacted to Dams in Windows 7 Version of Affinity Products?   
    @Ulrich Schroeder
     
    Apple users in 2000s: "Why don't you port this software to Mac? I don't want to run Windows. Please support OSX."
    Microsoft user in 2000s: "Well you bought a Mac. Deal with it, you shouldn't have buy one."
     
    Microsoft user in 2015: :crying:  :crying: "It's so unfair, no new cool App are available for Windows 7/8, WP or Surfaces"  :crying: :crying:
    Apple users in 2015: "Deal with it"  B)
     
    Enjoy your own medicine folks !
  20. Like
    Achim63 got a reaction from Adrian_M in Fill space between curves   
    Draw the three big triangles, convert to curves (if you used the triangle tool), copy all three and paste, then select Divide from Operations in the toolbar - voilà, there are your new triangles that you can color differently.
  21. Like
    Achim63 got a reaction from bassermann in Performance Issues on Imac 5k base model   
    I had some issues on my 5k after updating to 10.10.3, but those were connected to Spotlight (I had to rebuild its database completely since it didn't show andy search results). Maybe it's something similar on your machine, i.e. Spotlight rebuilding, which slows down everything for a while.
    I'd also suggest to buy anther 8 GB of RAM - that helps a lot in all regards (and it's much cheaper if you don't buy it at Apple as BTO).
  22. Like
    Achim63 got a reaction from MattP in Affinity Designer Customer Beta (1.2.0.24498)   
    Very welcome additions, thank you! Especially important for me personally: backward compatibility and "new from clipboard".
    The gamma adjustment seems quite effective as well, it will probably be used a lot by web "pixel pushers".
  23. Like
    Achim63 got a reaction from A_B_C in We need a German Forum here!   
    No, please don't. Then we'd need Spanish and French and Japanese and Russian etc. as well - and the developers would maybe miss important issues.
    How about opening your own German Affinity blog or something similar if you want to discuss the apps in German?
     
    Everybody should have at least basic knowledge of English by now, it's taught in school and you wont get far in any job without it anyways. It's such an easy language to learn (I find e.g. Spanish much more demanding regarding grammar and vocabulary).
  24. Like
    Achim63 got a reaction from AdrianKLægreid in Educational Price   
    I'd say it IS already available for an educational price for what it delivers ;-)
×
×
  • 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.