All Activity

I must say I concur with the idea of being able to link text files, particularly as I work with long form text. As someone said earlier, we can link graphic images but not text, which begs the question why not. Can this be added to the list of requested tools in the current or next beta releases. I'm pretty sure anyone using Publisher for working principally with text (rather than images) will be very grateful for the addition.

Apple never said it would replace a desktop/laptop it is a new category, I have all three but use iPad 95% of the time because it is convenient. Yes many special features need the desktop/laptop version but I can also do things on iPad that I can’t do on a desktop, e.g. I can’t export in HEIC format on the Macbook/Mac Mini, however I can direct from Affinity on my iPad using an IOS Shortcut. Simple.

I needed to get some drawing practice in and I had done a Robby the Robot a few years ago so why not the other robot designed by the same guy? The transparent parts were a challenge as they are curved and rounded. I used about 4 references, all had minor differences that will bother fans looking for a precise copy of the real thing but I am not even a fan of the show... just the tech. I mike do the Jupiter 2 spaceship and the Chariot transport of I find I have time.

This time I tend to disagree. If you do your DevSecOps properly and include a reasonable amount of testing, most new bugs would be caught and fixed before publishing as beta or retail. a fair amount of bugs can be identified by automated testing - just open some assorted test documents, take a screenshot of the result, and compare to the reference screenshot. Dead simple. In the company I work for we do a lot of Robotic Process Automation and Application Monitoring. (I‘m not in that Area, but use the service for monitoring some services I’m responsible for) The big issue of Affinity is the lacking of full scripting (of every UI function).

In general I wouldnt disagree with with what you are saying, but suspect that some bugs particularly associated with new hardware maybe difficult to repair without a major rebuild. Every new dev cycle introduces more bugs, unless a complete from scratch rewrite, which has its own new bugs it never ends so must be satisfied with core and commonly used functionality to satisfy ROI, as you say perfect.

In your Photo Settings, under Assistant Options, what RAW Engine are you using (bottom left of that dialog).

I wish you luck, as I agree with your comments regarding Microsoft. However, as I'm not sure it will happen given the previous responses, wouldn't it be more worthwhile trying to aim for more organisation and focus in the FOSS community and to come up with a plan to fill the holes where creative-focused software is lacking on Linux? The first step would be to have a clear plan of what's needed on Linux, the next step would be to discuss methods of obtaining grants and other funding to make it happen.

I would start by clicking More in the Context Toolbar and checking the details of the brush design. It looks like it is not applying the color at full intensity. Perhaps something to do with the image used for making the brush head, or the Accumulation setting. Or, as an experiment, use a hard round brush from the Basic category and see if that works better for you. In other words, I don't think it's a color issue.

It would be interesting to see a comparison of other models.

My iPad Pro 2017 16.5.1

Being aware of bugs at least allow a decision to be made, whether they are worth pursuing..Reporting of numerous bugs would apprise devs which are effecting the most users, allowing them to prioritize their efforts. I suspect that security on Apple devices, is problem, devs have to constantly circumnavigate. This is further support for my Pizza restaurant business model as mentioned in other posts, which would allow for core and commonly used functionality to be relatively bug free. Yes, exactly what I meant regarding software dev, push it out the door.

I’ve just repeated developing the CR2 with the same results again. I am using Affinity Photo 2 2.5.0.2437 on an iPad Air3 - iOS 17.4.1. Is this a difference between iOS and Win programmes?

This thread is yet another duplicate:

After about 10 years of Affinity Apps at least for me it is clear that Affinity has absolutely no intention to fix (or identify) all bugs in the way e.g. of D.E. Knuth handles bugs (in software and books). The number of documented unfixed bugs is the dimension of several hundreds or thousands, and the pace of bugfixes is far slower than new bugs gets observed. Affinity was a promoted App by Apple during launch of M1 silicon in 2020, and it is painful that some M1 related rendering bugs seem to not getting fixed before this generation is rated obsolete after 5 years next year. I‘m affected both with Mac and iPad. So I get to the conclusion that Affinity is not even interested into getting all bugs documented, as this creates effort on Affinity side for user support, and development. Many bugs affect only specific platforms or rarely used tools, so this approach seems to work in general as bugs lading to crash or corrupt files get some attention and fixes (later than sooner). New features seem to get more ROI vs bug fixing, and 80/20 is the new „perfect“.

I disagree, but are you advocating against incentives for my premise of offering rewards that users assist in making a product better? Just curious, why are you here? I’m here because I like the company, and their products and like to see them get better and succeed. ps Wasnt Aldus a software company that originally created desktop PageMaker and vector based Freehand, and was later purchased by Adobe? https://en.wikipedia.org/wiki/Aldus_Corporation

"What Snapping options do you have enabled?" 😳 A: None, you'd think it would be "ON" by default... so thank you! I'm so used to deselect options I simply hadn't thought of it being "reversed". Thank you for replies, much appreciated

Discount is still payment, reward. And no, you simply cannot compare companies in such a generic, overarching, and apologetic way. That is certainly not my long experience with companies. Read around in this forum. There is plenty of feedback for Serif on this point.

My iPad mini 6th gen

For first: Thanks to all responders for all the answers. Educational. On average about the artwork in Publishers; Often 'just' posters and flyers, very occasionally books and manuals. I work with iMac 27" Late 2015 with 24GB on-board (and SSD) and Macbook Air 13" 2015 with 8GB. Both devices work well, but it is a good idea to look ahead. iMac 24” + MBA 13” M3 or iMac 24” + iPad Air 13” with keyboard/pencil (same budget). I think so it’s better to buy a MBA 13” (16GB), maybe with refurbished iPad Air 2022 and pencil for drawings and others. Anyone else who worked with iMac 27” for a long time and now works with 24” iMac with Affinity? Yes, Apple doesn't make it easy for us. I have difficulty with the idea of going from 27" to 24" if I choose that iMac, but that is not relevant to this topic.

I wasnt suggesting payment, but merely discount having reached established reporting limits. Market pressure always pushes developers to release products early they even advertise features they dont offer..YET, then push devs nose to the grindstone to get it done. and then rely on users to help fine tune and debug. Thats software development.

Hi. Thanks for abiding my dilettante ways. My Publisher skills are pretty spotty, and I was trying to pin a text frame to another text frame, but I can't. Seems like my document is only allowing pins of elements in groups of layers, which may well be default and sensible behavior. But I can't drag this element into the group in question AND if I duplicate an element in the group, it is duplicated above the group and...can't be dragged into the group. I can reorder the element anywhere else on the page. The document has no master pages, and none of the layers are locked. I have no doubt the answer is something very obvious, and I thank anyone who might give me any of their time or attention (or point me to where this issue is addressed).

Try before buying. Hands on. Your hands. I would go for the laptop, personally, if I had to select just one. Especially if I was to work in Publisher or the like. To Hell with the spec comparisons. It's for kids. All recent Apple products are more than fast enough. You need to consider the interface, workflows, collaboration with other applications, accessing files from different sources, printing, everything, simply everything in all workflows. And especially really, really large documents and performance. An iPad and a laptop are two completely different universes to work in, and if you are even slightly serious about what you do, then you're most interested in having the fewest possible bumps in the road in your particular way of working. An iPad is a fascinating little slab, mobile and more flexible in some situations, and with M1-M4 it has gotten plenty of muscle, but it's not a laptop. It's a large smartphone with a different—and heavily truncated—operating system, and you should also investigate the support for external displays. Affinity is behind too. I always choose my MacBook when I go out, it takes up no space and weighs nothing, it is so rare that an iPad makes more sense. However, I can connect my MacBook to any kind of display, wherever I am, and then I have a full-fledged computer again without limitations. The iPad was predicted to kill laptops by the geniuses in media and on the internet. I see leaders taking it to meetings the most, and I see creatives with MacBooks everywhere, they are scratched and worn because they are with them everywhere. But I absolutely haven't seen them replace a thing. Rather, they find their own place as accessories and extras. Those I know who get something out of an iPad Pro are people who use it for precisely those fields where it has its few but significant advantages. Bought for a specific purpose. However, it is not desktop publishing, and funnily enough, they also have a MacBook or a larger Mac. Always.

It's a permabug. When Transform Objects Separately is enabled, Power Duplicate should use each object's transform origin (either the crosshairs Transform Origin when that is enabled or the selected point of the 9-point proxy in Transform panel) when transforming each object. However, the transform origin of the key object (the one object with transform handles displayed) is wrongly used for each object instead. The bug has existed since the v1 days and I believe it was acknowledged and put on the developers 'to do' list years ago.

Yes, and one shouldn't be too proud to build on a good idea from someone else—especially not just to be different. It works excellently in InDesign.