vonBusing

I believe some improvements/adjustments have been made on gradients and their pdf-export over thew last two years. So, yes you might expect things to be slightly different. Especially radial gradients should now be exported as vectors rather than rasterised as they would previously in AD. If the gradient looks as expected within the native AD file, you might try to duplicate the actual object and rasterise it before pdf export (keep the original object copy hidden for future adjustments). That should give you a similar exported output as the one you had initially. One reason for differences between native rendering and pdf export could also be of the color space of the colors used to define the gradient not matching the color space of the exported file. A conversion is done during the export. If that's not the case, it could be a bug that Serif needs to look at.

While I do not think animation capabilities is especially on-spot for a DTP, data merging definitively is. I understand that this is not an easy task and that it might not be a priority pick for the initial push of the software, but I do hope Serif consider it for future updates.

While waiting for A Publisher, I have started to use AD to create folders of typically 4 - 12 pages for the last couple of years. When multiple artboards got available, that was made possible. Although, I would not want to move further than 12 pages with AD, because page management is basic at most (no page numbering, no spreads...). As you said, text formatting is lacking some basic functions like lists. But still, the ability to easely export the whole thing into a print-ready pdf with bleeds and adequate color management has been the big incitement to do the work in AD anyway.

Hi Amanda, I think the behaviour is the following: If the object is within the artboard in the layer pannel, then it will be hidden if it is moved outside the artboard area (but still with some edge contact with the artboard). If the object is outside the artboard in the layer pannel, it will be visible as a free object outside the artboard. Mostly, objects moved "far" outside the artboard area are also moved outside the artboard layer. Moving an outside object back over the artboard area will put it automatically inside the artboard in the layer pannel as well. I'm not sure why the objects are disappearing (not only hidden) in your movie, though. Are you sure you are not pressing a key while deselecting one of them that actually deletes the object (since they are also completely vanishing from the layer pannel)? Also, why don't you update to the current version (1.6.1)? Maybe that's a bug that has been fixed since the 1.3.x version you are using.

I can confirm I see the same glitches as G.M.1986 when using a secondary display (non-retina) on my MBP 2013 (retina), macOS 10.12.6. It happens most often when reconnecting the display while AD is running. It is a little annoying, but closing and reopening the misbehaving document usually resolves the issue. Another, probably related glitch, is the content of the document being suddenly rescaled to 1/4 of its size (1/2 height, 1/2 width) on the external display, and being impossible to rescale to any other size. The solution is, here also, to close and reopen the document.

So very British

Previously, we were told that the beta program should start by the end of 2017. Since it usually takes quite a few month before the sharp version is released, that makes it still possible, doesn't it?

Thank you Patrick for your explanation. It does make sense. So we'll have to wait for the 1.6.6 update on the iPad for a light UI, I guess. (Although, I have been quite comfortable with the dark UI so far. Not sure if I will switch)

Where did Affinity Photo 1.6.0 go? I must have missed something, but I can't find any comment on this in this thread nor in the beta forum. Both Affinity Designer and Affinity Photo are moving from 1.5.x to 1.6 versions, and, while AD starts at the logical 1.6.0, AP jumps to 1.6.6. This is of very little importance, but still tickles my OCD somewhat.

Having this line is very useful for bleeded documents.

Thanks MEB; good to know that this is logged, because quite devastating. I noticed that the issue was still present in AD 1.6 beta 1, though. Meanwhile, I figured out that using the contextual toolbar to add a given CMYK-colour to an object and then use the "add current fill to palette" symbol in the Swatches panel, was a much safer way to build up a palette. /Miro

Even worse: dragging any colour value controls for the CMYK-colour, deletes palettes colours at the speed of the running band. I just annihilated 90% of my hard work adding named colours despite the bug mentioned in my previous post. No "undo bug" function was found. :blink: :wacko: :o :(

When I edit the CMYK values of the fill of a palette colour, AD actually deletes one colour from the palette for each value I edit. That was not expected. See this screen capture: https://www.dropbox.com/s/g8z69xqu0fh9yve/color_palette_edit.m4v?dl=0 In that case, 2 values were edited and 2 colours vanished from the palette. If I edit all 4 values, 4 colours are gone. The way all the colours vanishes in the background when editing is also unexpected (temporarily, though - a little scrolling does restore the ones that have not been deleted). AD 1.5.5 macOS 10.12.5

Except the fact that the beta actually stops working, this is sort of default behaviour in macOS and nothing specific to AD and ADB. Each single file can be tied a specific application even when several apps that can open them, are present. You could view the Get info window to any AD file and set AD as the "open with" application and be sure to "Change All..". Alternatively you could just throw away ADB until next working version is made available.

Hi Jens, This is a known bug for at least quite some time. Until this is fixed, there is a work-around, if you do not have too much text involved: duplicate and convert the text to curves before exporting (unselect the text object - good to have if edits are needed). Remove then the bad nodes from the text curves that are causing the problem. (see picture in my post linked above) Otherwise, you might want to try to tweek with the eps export settings ("more"-button in export dialogue ) to find a combination where the bug does not quick in. (rasterising options might help but maybe not what you were looking for when choosing eps format). /Miro