AndreaR

Nevermind... I just forgot to setup Apple RGB to document's colour profile. How silly of me...

Hello, do someone knows why when I apply a given RGB colour to a shape (while designing an image for the web), if I get its value with Apple Colour picker, it gives me a different RGB result value? To replicate my issue, just open Affinity's Colour chooser on any colour, and then pick the colour with Apple Colour picker, then you see they are different RGB values. One example is FF4AD0 on Affinity's chooser, that Apple's one picked up as FF00E5.

It may be a corrupted installer? Dunno if the downloads have a md5 or sha-1 checksum near them, it will be a good check.

Glad you had found the culprit :lol: Other than loading raw slowly, I've witnessed on some random times the app will "think" some seconds before refreshing window. Dunno if the cause is the same, will replay my test workflow after raw loading is fixed, to see how it goes ;)

Got it straight away as soon as it appeared on the MAS :lol:

If you go back to use some feature (still) not on Affinity, you may take a look here and ask there anything you feel Affinity needs to handle, if no one requested it before ;)

Out of curiosity, I always see any photo product have its own RAW import compatibility. The RAW support I see Apple release every now and then on their system updates, cannot be used for imports from your (or any other developer's) app ? I just wonder why every image app developer have to reinvent the wheel when it comes to RAW imports :P

I got the Huion H610, really awesome tablet in the price range! I'd like just have more control on low-pressure, the default stylus does jumps 8 levels at time from 0 to 300, and that is the place where I land in the most. Any suggestion for a finer low-pressure stylus? Edit: it were a wrong sensitivity setting on my software, that made me see stepped sizes on pressure. Once setup that correctly, I will not notice that 8-stepping at all and stylus is working fine!

AI is Adobe proprietary format, and it is very unlikely Adobe will license the format to a competitor. That is the very reason it is already some years it were put so much effort on "open" file formats. Imho, it is better concentrate efforts on SVG and maybe propose updates to the specification, to be able add all info that still cannot be placed into SVG today, thus the need of proprietary formats. I may be a visionary, but I really want see one day a digital world with very few file formats, all of them open, and every software developer concentrate more on its product than the file format of load and save. We still are far from it.

As long as Bridge is a separate product, you can continue to use it. Or you asking for a Bridge substitute? I think it is better use a dedicated product, rather than something integrated on an image edit software. So I will be free to use my editing software of choose without touching anything about my assets. That makes me think it will be great have such a piece of software, dedicated only to the asset and metadata management, I only can guess that will be a tool of far better quality than all things I see on the net, that they are "do-it-all" but excels on nothing.

Linux, even today on 2015, is still light years back on terms of usability and ease of use. It is already difficult concentrate and do well my job, and the need to deal with console and 'su' commands every now and then, is a no-no on my side. Even if AD ported to Linux, I will stay here on Mac, because I'm quite scared to have to deal with a Linux distro to do my job everyday. My opinion, Linux is perfect for machines dedicated to one-specific-task, but to general purpose use, is so far away to even consider it an option. Last but not least, developing on linux is quite an hassle, you have to deal with a number of distros, multiplied a number of user interfaces, multiplied a number of different ways to provide updates. If you choose of all that, the one you want follow, you will go to a niche of an already small market (intended as general purpose paying user base).

To me, will suffice have an "User" swatch that I can save and load, so I can keep together the colours I need for each project and organize them in separate files. If the actual user swatch is also saved within the project file, will be the great: I open the .afdesign project and my user swatch already filled with all my colours :)

Yes, correct, as "before export" I intended the option to turn on pdf export settings. That the reason I pointed you can keep text into the original project. Thanks for clearing better things up^

Hi, I had to face that when sending to print, text with images. AD have the nice feature to convert text to lines before export. This also will assure you that the print is exactly the same as you see, as long as the text is exported as vectors and no more text+font, without all the issues about how a font is rendered on different systems. You will want to keep text in the original project, instead.

Hello all, how can I make the PDF export save my project as multipage pdf with one page for each layer I have? That is useful when I send files for printing, my two layers are front and rear views. Actually, my workaround is save the two layers in separate pdf files, then I will merge the two files using another tool. Andrea