Jump to content

Herbjul

Members
  • Content Count

    11
  • Joined

  • Last visited

About Herbjul

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. No more Problems with RAW or JPG. And even shorter loading and saving times
  2. Change and Rename Photo -doesnt help -Affinty exetsnion load no picture from OS X Photo Move Photo to somewhere else -doesent work What is the latest status when the hoped-for beta will finally be released? I suspect the Feler in the memory process of Affinty Photo. A file can be loaded and edited, but saving and overwriting the retrieved file doesn't seem to work properly. In the folder where Affinity stores the files for caching, the old and edited versions are stored. The same goes for the Affinty document file. So far so good... Saving and closing the tab Thumbnail is updated error message Slowly it gets really embarrassing. The massive bug has been around for almost 6 months and will work in beta or workarounds. Older versions from Timemaschine show the same problems (version 1.7.2) Offebar has been added in the newer version 1.7.2 to 1.7.3, which causes these bugs and they still exists
  3. UI elements disappear when calling the Konetxt menus
  4. No beta in sight yet :-(. Strangely enough, the reference to the upcoming version 1.8 is included in the Publisher Beta Info. That was almost 2 weeks ago
  5. Extremely bad news OS X BETA 10.15.2 has the same bug. Apparently the bug is on the software side in Affinity Photo standard 21:53:30.661813+0100 runningboardd Invalidating assertion 580-268-271 (target:executable<Affinity Photo(503)>) from originator 268 standard 21:53:30.812032+0100 runningboardd [executable<Affinity Photo(503)>:2298] Ignoring jetsam update because this process is not memory-managed standard 21:53:30.812105+0100 runningboardd [executable<Affinity Photo(503)>:2298] Set darwin role to: UserInteractiveNonFocal standard 21:53:30.812155+0100 runningboardd [executable<Affinity Photo(503)>:2298] Ignoring GPU update because this process is not GPU managed Failed to save content editing output <PHContentEditingOutput: 0x600001a1d220> adjustmentData=<PHAdjustmentData: 0x60000262db30> identifier=com.seriflabs.affinityphoto version=1.0 data=0x6000029cb460 (0), renderedContentURL=file:///var/folders/my/r72_4p2x53j2c171rt68_t_00000gq/T/com.seriflabs.affinityphoto.AffinityExtension/RenderedContent-F5F25481-788F-430B-96F5-50772627FCEE.JPG, renderedPreviewContentURL=(null) with error Error Domain=NSCocoaErrorDomain Code=-1 "(null)"
  6. Error Message in OS X Catalina Console Failed to save content editing output <PHContentEditingOutput: 0x6000033c7340> adjustmentData=<PHAdjustmentData: 0x600000e7c240> identifier=com.seriflabs.affinityphoto version=1.0 data=0x6000000124c0 (0), renderedContentURL=file:///var/folders/my/r72_4p2x53j2c171rt68_t_00000gq/T/com.seriflabs.affinityphoto.AffinityExtension/RenderedContent-3EF0BC90-7FDE-4B37-947C-C2F30BB912B2.JPG, renderedPreviewContentURL=(null) with error Error Domain=NSCocoaErrorDomain Code=-1 "(null)" Hope this helps the developer Team to solve the Problem
  7. Hoffully there is an better development for epub-Data and Footnotes than in iBook Author. iBook devolp no Footnotes
  8. The same Problem at my Macbook too :-(
×
×
  • 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.