rui_mac

Is there any way to use a path (freehand path, or parametric vector shape) to guide a "painting" tool? I placed "painting" between quotes because it could also be a Blur, Sharpen, Smudge, Dodge, Burn... tool. If there is a way, I haven't found it. When creating a new brush, there is a drop down to define an associated tool but I can't seem to find out what it does. And, if there isn't such an option, there should be one.

I'm a loooooong time Photoshop user. And when I say "loooooooog time", I mean I started with version 1.0 of Photoshop. Although I still have to work with Photoshop at my workplace (since the agency where I work, uses the Creative Suite), at home I use Affinity Photo (except for work having to do with intensive alpha mask work, as Photoshop is still much, much better at it). However, I do try to transition as much as possible to Affinity Photo, for all bitmap related work (I fully transitioned to Affinity Designer for all my vector work). But I still find some things that I have to admit that Photoshop does better and the Dodge and Burn tools are some of those things. Take a look at the attached image and tell me what you guys think.

This is one of those things that would easily be possible if scripting was available.

I have my Recent Files option in System Preferences > General set to '10' and I still get no recent items list in the "Open Recent" option of any Affinity application. I'm on Mac OS Catalina (10.15.7).

+Googolplex ... for the blend tool.

+1 We really need a way to make it easier and, above all, more accurate.

Thank you. It worked!!! But I was hopping that the Locate button would tell me where the error was. The Find/Replace worked but didn't showed me where the missing font was.

I have an Affinity Publish file that, whenever I open it, warns me that a font is missing. When I select it in the Font Manager and press Locate, nothing happens. Also, choosing a replacement font and re-saving the file does nothing, as it tells me that there is a font missing the next time I open it. How can I clear this error?

Thank you so much. I assumed that it wasn't possible because as soon as I turned off the Separate mode, all my studios that resided in my second screen were all gone. I created a new studio configuration for my two screens now, using non-Separated mode. Thank you so much.

I work on a two-screen system, so that is not and option :-(

I don't know if this qualifies as a bug, but whenever I open a document in Affinity Publish, I get that document in a windows that I always have to resize manually to fill up my screen space. I can't even use the zoom button (I'm no MacOS) because doing so, makes the windows expand to the whole screen and the top of the document ends up behind the top toolbar. Is there any way to make Affinity Publish remember the window size so that I don't need to re-scale the document window each time I open the document?

Python or javascript, as it works in any platform. If I create a script/tool I wan't it to be available on MacOs, iOS and Windows, without having to re-code it. I also don't want to look out for scripts/tools and realize that they only work for an OS that is not the one I'm using.

Thank you!!! That was it. Now it only reports spelling mistakes, because I had to include some english words in my Portuguese text

Here are the captures of a snippet of a text box (with Portuguese text), a capture of the Character Language options and a capture of the Profiler errors. It has lots of these "Missing dictionary" errors.

I have the same problem. My text is REALLY in portuguese and I get all these "Missing dictionary" errors. What do they mean? Is there really a dictionary missing? The text boxes are set to the Portuguese Language and I have no red underlined text. However, the Profiler still states that Portuguese dictionaries are missing.

Freehand had an amazing blending tool. I even made a video showing it. And I'm sure Serif would make it even better. https://www.youtube.com/watch?v=F3Rh8OcI9zU

So much could be done with such a tool. And I know Serif would make something wonderful. Much better that the blend tool of Illustrator. Come on!!! It has been asked for since Designer was in beta

Some applications only import vector files in Illustrator 8 format. For exemplo, Viz Artist (the application that I use at the TV station I work on) has a plugin to import vector files, but it requires Illustrator 8. It is a very old format and I believe it is well documented, unlike more recent Illustrator formats. But, for apps that onlu require basic Illustrator format, the Illustrator 8 format is usually the standard. Couldn't this be added to Affinity Designer?

It crashed with any curve that I draw by hand, wether it is closed or opened. As soon as I drag a little more to create a larger contour, it crashes.

Ok. I will create a new file where the error can be reproduced and create a new thread.

The Contour tool crashes consistently when I try to create a large contour on an hand drawn open path.

Better yet, and it would provide a "parametric editable power duplicate" would be a powerful Blend Tool.

Do you know how the data structure is stored? Is it a list [witdth, height, 2] matrix or two [width, height] matrixes? And, no matter how they are stored, they are two matrixes with the same structure, containing the same data type values. So, once again, there is no excuse for not being able to perform the same operations on a "opacity map" matrix that can be performed on a "greyscale" matrix. I'm a coder and I know what I'm talking about. One of the last plugins I coded as a 3D vertex painting set of tools. It deals with RGB and, optionally, with an opacity map. The same set of code that is used for each of the R, G and B channels (that are, fundamentally, three greyscale channels), is the one I also use for the opacity map. I even coded Dodge, Burn and Blur tools and they work the same at the RGB level as they work at the opacity level.

If you pay so much attention to definition details, what would you say that the individual channels of an RGB image are? Chromatic? Or achromatic? Because each individual channel has no color information. It just contains a list of values that define the intensity of each individual component. Just like a greyscale image is just a list of values that define the intensity of light of each pixel. Just like an alpha is just a list of values that define the opacity of each pixel. If they are all the same (and stored the same way, internally), why can't you perform on an alpha channel the same operations that we can perform on a greyscale?

The greyscale values are just a single list of values. A "greyscale LAYER" includes the greyscale list of values and a n opacity list of values. All layers include an additional list of values for the opacity. So, a greyscale LAYER is simple a set of two "greyscale" lists. And an RGB LAYER is a set of four greyscale lists, one for Red, one for Green, one for Blue and one for opacity. Once again, there is no excuse for the opacity list (call it alpha, or key, or mask, or opacity map, or whatever) that is merely a list of values just like a greyscale image or any of the composite channels of an RGB or CMYK image, to be treated differently. In a nutshell, an alpha channel is exactly the same as a greyscale image and should be treated the same way, allowing all tools and operation that a greyscale image allows.