cadobir

OK, I've rechecked, and they do work close enough to the way Photoshop does it to be useful to me. Thanks for your feedback, everybody.

Dear Affinity programmers, I am quite sure that you know all the reasons that people want you to add Bitmap Mode, aka 1-bit color, to Affinity Photo, but here's the brief synopsis: works created on paper must be scanned and adjusted in a photo program. That includes calligraphy, illustrations, cartoons, and more. Bitmap mode is needed to engravers, platemakers, etchers, and is often needed in layout programs for spot color assignments. I am not a programmer and have no idea how hard it is to add bitmap mode, or to just turn off antialiasing. But I wish you would do it. I want to make Affinity Photo my primary photo editing app, and I can't, because I need bitmap mode. This is really important to me. Please add bitmap mode. Please!

YES!

You may be right... but 1-bit graphics are still very important for certain vital sectors of graphic arts. And since a good part of the original artwork for that sector is created on paper, it has to be scanned and treated like a photo, which requires... a photo app.

"Black and white line art is, in my opinion, more appropriately dealt with in Designer, not Photo." When the original artwork is pen or pencil on paper and the linear has to come directly from the original art and file size is a very important issue, 1-bit color in a photo app is critically important. Think of calligraphy, cartoons, and other applications. It may shock you to learn that there are still people who insist on working on paper, only to have their work digitized, but that is the reality.

I recently did a job where, to fill an object with a pattern, I had to hand-assemble the pattern. And then, because the pattern needed to be warped to suggest a contour, I had to rasterize it, export to Photoshop and warp it there (Yes, AP might have done, but I was on deadline and I'm more used to Photoshop). And then, because I needed to be able to manipulate the pattern as vectors, I had to re-vectorize it in Image Vectorizer (which did a pretty lousy job). The whole thing took almost a day. Part of the time was spent in experimenting with drawing vector shapes to my own custom guidelines - a failure. Vector fill patterns, and even more, Vector Warp would have saved me hours and the client money. I hope this feature will be added soon. If not... I guess I'd have to go back to Illustrator, which I hate.

I've tried some workarounds for Offset Path, and they are unsatisfactory - time-consuming, complicated, and inaccurate. I would really welcome an Offset Path function.

When I’m working out variations on designs for clients, guides spanning artboards would help me keep my artwork aligned without having to duplicate the contents of an artboard and then alter them. While we’re talking about artboards, the combination layers/artboards panel quickly gets cumbersome when I have three or more artboards in the works, as happens when I’m designing a media campaign. A separate palette for artboards might help clean things up and make the work go faster.

5 years later... This is still actually a problem. It's not wrong to hide the parts of objects crossing the boundaries of artboards WHEN THE USER WANTS TO. It should be switchable. And it would be VERY VERY USEFUL to have guides that span multiple artboards and are visible in the... pasteboard, is that your name for it? Drawing table? Background? Anyway, having the artboards force a crop inside the program, while I'm working, can really get in the way.

Thank you. I finally just now stumbled upon that answer myself - something I was unable to do while trying desperately to turn in vector art on deadline, and failing because of this issue. Perhaps it would be a good idea to make it impossible for dashed lines to appear as solid lines.

I’d find it very useful if objects, including guides and grids, could span artboards. Perhaps guides and grids could exist independently of artboards, and artboards could snap to a base grid.

I've been working on a drawing for an engraver to make plates, with the art 1.3125 inches high and about 2 inches across. It's a very complex file. The engraver needs color separations and a bump map and prefers to receive vector files. I was going about collecting the elements of the file and converting strokes to fills to meet specs, when suddenly AD started failing to make this conversion. I don't know why, but it cost me a lot of time, forced me to deliver raster assets instead of vector, and nearly cost me the job. If I had had time, perhaps I could have re-drawn the difficult items and had success with them - I don't know. But I didn't have time, and this should simply not have happened. Here is the offending artwork, a very small but important part of the complete drawing. I would be grateful for guidance, and much more grateful for Affinity to fix this issue. Curves wont expand.afdesign

I'm just finishing up a project in which vector warp, distortion, etc, would have saved me at least an entire day of work. It would be really great if these features could be added sooner rather than later.

I am running Affinity Designer 1.8.6 on Big Sur on a mid-2017 27" Retina iMac with 4.2 GHz Quad-Core Intel Core i7, 64 GB 2400 MHz DDR4, and Radeon Pro 580 8 GB. Working on a fairly large document with 3 artboards, multiple drafts of various parts of an image, little bitmap content, and an output resolution set to a custom 1200ppi. The document is stored in iCloud, but I don't think that's much of an issue. I do have several other programs running, so not all RAM is available all the time. The problem is that, in this document, I create a line and choose the dashed line options and nothing happens. I was able to create a dashed line in a new document and copy-paste it, but that's a workaround, not an actual solution. Can you help? I do not believe I can include the file, as it is for a client who has lots of lawyers.

Can Publisher derive Table of Contents from filenames? I'm just starting to investigate the TOC function in Publisher, and I see the choice to "Look In" All Text Frames or Text Flow. But I'm putting together a book of sheet music - all PDFs generated in music notation software, complete with titles and citations. There will effectively be no written text after the title page. Moreover, the same need might apply to a book of photos. Any help to be had, or am I going to have to compile a TOC manually, which would suck?

Thanks, I figured that out. I agree that it's not as good as having some sort of Not Printable/Not Exportable layer on each Page and or Master Page. I hope it's not too hard to implement; it's a very valuable feature. By the way, to TURN OFF Master Pages so that they don't print, YOU HAVE TO TURN THEM OFF ON EVERY SINGLE PAGE.

How can I designate non-printing objects or layers in Affinity Publisher? This is a very important function for creating design aids such as page numbers that will not be printed or other regularly-occurring features that should never appear in print or export. If it is "on the roadmap", when can I expect it to be implemented? The absence of this feature is a serious roadblock to my successfully using Affinity Publisher as my primary layout program. I have tried placing objects outside the margins, to no effect. I do not want to use a bleed as a place to hide stuff. I need to be able to create non-printing objects both document wide and on a per-page basis. Please respond. Thank you.

I too could really use an efficient way to batch-rename or batch-edit layer names. I often have to import a group of photographs of the same subject or the same type of subject into a master document. Those photos may be moved up and down the layer stack, or dispersed all over the master document. I have to be able to track them. Better yet, when I have more than 25 layers, I need to be able to search them, by name, content type, or attributes such as blend mode.

My layer names are more complex, but I need the same functionality. I have to do a fair amount of FPO photography of may items in a single shot, then separate the items to their own layers. But I still need to refer back to the original photo for every one of them, and I want iterative names like "Red dots 1", "Red dots 32", and so on. Batch renaming would make my life much easier and enable me to move more of my workflow to Affinity software.

I second the request for a feature to search and/or sort layers by name, type (pixel or adjustment), blend mode, etc. For my work it's critical.

It would be great to be able to designate layers as non-printing, as you can in InDesign and some other advanced graphics programs.

I see that bleed area guides have been on the feature roadmap for Design since summer of 2014. When might we expect to see this feature?

I'm trying to set up a file management system for a very prolific artist who likes to change teh titles of his works often. One of the ways to embed and protect the data so that I can find images when he requests them is to embed the data in the description field of EXIF. I'm sorry to say that it looks as though this feature has barely been given even glancing attention in Affinity Photo. The EXIF panel is not particularly easy to find. The data it contains may not be editable. The Description field is editable, but has no "undo" functionality. This is a very serious shortcoming for a professional imaging program. May we expect an improvement in this area soon?

Still not changed as of AD 1.5.5. This really slows down my work. Please, Affinity - can you make guides tool-agnostic?

I have just been working on a file in AD 1.5.5 on Mac OS X Sierra 10.12.5, and discovered that there's a very handy keyboard shortcut for incrementally increasing and decreasing numerical values, for example in font size: Option + up or down arrow. --> Unfortunately, even though I am using this shortcut in a dialogue related to text, the shortcut works on the text itself simultaneously, by changing the leading override. Oops! --> Also discovered that while the text tool is active, I cannot use keyboard commands to zoom in and out of the document - Command = and Command - are temporarily disabled.