Jump to content

Scazzino

Members
  • Content count

    6
  • Joined

  • Last visited

  1. Thanks for confirming the bug! I had searched for Bug Reports on the forum before posting, but I didn't find an area to post bug reports so I posted here. Sorry about that. Can admin move the thread to the proper forum?
  2. I've come across what appears to be a bug in Affinity Designer 1.7.2 on Mac OS X (10.11.6) I've created a multi-layered symbol which includes an Exposure Adjustment Layer set to 1 I have another layer that uses a number of symbols including the one with the Exposure Adjustment Layer. If I then clone that layer which uses the symbols and detatch all the symbols. Then the Exposure Adjustment Layer in the now detached instance of the symbol reverts to a setting of 0. I've stripped down and simplified a bug test scene to reproduce the bug. These steps should reproduce it. * Load scene BugTest_1B * Open the Presentation Artboard Layer so you can see the sublayers * Open the Set 00A Group so you can see the sublayers * Select layer Letterhead Front Symbol inside the group SET 00A * Detach the Symbol Here the image in the Presentation Artboard gets darker, because the Exposure Adjustment Layer in the now detached version of the symbol reverts to 0. BugTest_1B.afdesign.zip
  3. OK, uploaded. They are just low resolution rough test files with a soft edge to the transparent area. Just scribbled the transparent area to test the edges in Affinity. Both were saved as TIFF from Photoshop CS4 (11.0)
  4. I'm running into white halos around grayscale masks that are part of transparent CMYK TIFF images when placed in Affinity Designer 1.6.1. Here's a sample of a transparent TIFF that was exported from Photoshop as a CMYK and RGB TIFF that are subsequently placed in Affinity Designer. Notice the left one (CMYK) has a white halo around the hair. The exact same transparent TIFF placed back into Photoshop show both the CMYK and RGB versions with no halo (two on the right).
  5. Scazzino

    Failed to save document:

    Thanks Sean, That's pretty much what I figured from researching this problem on the forums. Perhaps they could implement a remote workflow feature, where the user had the option, through a preference setting. When activated it would cache the entire file when first open and reference the local cache while working and then save back to the original during a full save. That way a disconnect would prevent loss of work. You could use all the same code you already have while working, just point it at the cache rather than the original file. The only major change would be adding an initial file copy to cache during the open function and a clearing of the cache on closing. Any word on the other issue about the modifier keys getting stuck when trying to work remotely via screen sharing?
  6. I often work on my MacBook pro remotely connecting to my 12-Core Mac Pro via Apple Filesharing. I use many different programs this way. However whenever I try to use Affinity Designer 1.6.0 this way saves often fail forcing the document to close and losing work. I keep getting the following dialog. Failed to save document: DocumentName Save failed because access to the file was lost. The document must now be closed. (OK) Then of course clicking OK closes the document, losing my work in the process. It's very frustrating. I'm running Mac OS X 10.11.6 on a 4-core MacBook Pro where I'm using built-in Apple Filesharing to connect to a 12-Core Mac Pro. The files are located on an external 3TB OWC Raid connected to the 12-Core Mac Pro via the built-in USB-2. This only happens to me when accessing the drive via filesharing. It does not happen when accessing the drive locally on the 12-Core Mac Pro. Since this fails so often I then tried to use built-in screen sharing to just run Affinity Designer on the 12-core Mac Pro but do so remotely from the MacBook Pro over screen sharing. That then encountered another bug. When running Affininty Designer via screen sharing it often gets confused thinking that modifier keys are pressed when they are not. For instance clicking on an object layer and moving it causes it to create a new layer as if option-drag was used, when it's not. Clicking on a layer in the layer palette and then clicking on another layer selects them both as if I was shift-clicking when I'm not. Pressing the spacebar and dragging to pan the viewport gets stuck so that it then thinks the spacebar is still pressed after it is released. Etc. Due to these two issues I cannot reliably use Affinity Designer remotely. I often use many, many different programs in both of these ways, via filesharing and via screen sharing, and have not encountered either of these problems in any other programs. I'm connecting the MacBook Pro to the Mac Pro via Wi-Fi.
×

Important Information

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.