bt1138

I was just trying to do the same thing, for the very same reason, old scans of pages, want to make a single pdf. This would be a very nice feature to add to the software. Data merge and .CSV to file path? Is this Linix, help me, please. Anyhow, Any PDF decent editor can do this. But the files I have are in JP2 format and most pdf apps can't read them. The Affinity apps do. So I batch converted them to png using Affinity photo and then combined them in Foxit PDF Editor, but there are many other pdf apps that will do this too.

"the specific error with failure to perform the bool op is down to edge case calculations as a result of possibly only one or two curves in the font glyphs. This will be rectified in 2.1." It's pretty amazing that there are people in the world who can figure stuff like this out. Thanks, @Ben

What it says, I assume it's due to using MSIX format. This is a standard behavior for programs for at least 20 years now. Any way to make it work? *edit: Yes, as some surmised, this is for a file being dragged onto a shortcut on the desktop

I just did the full upgrade for all 3 pieces. Yeah, it's probably not really a huge improvement. But there are improvements. At $33 per app, it's a totally fine transaction in terms of value for price. And yes, people do need to pay for this kind of thing occasionally, or you can complain when it all goes onto subscription and bitch about that. As far as abuse goes, the main software I use in my profession costs $4,000/year subscription and they change the file format every year, or rather lock out backwards compatibility and everyone bitches that they never improve it (in fact subscription seems to sprout at the moment that software stops evolving and people stop upgrading). -->Serif is nowhere near what abuse of software lockin really looks like.

This is all because the 2.0 products are Windows "MSIW" apps. Affinity is the first app that I actually use that is in this "New" format. It seems that a lot of / most other applications don't recognize the format of the new program type and it's shortcuts. It's probable that the other software will have to be updated to get them to work with these apps.

When you consider how little affinity charges in the first place, it's not out of line at all. Someone has to pay the salaries to keep it working and maybe add features now and then...

I don't care about the icons, I'll get used to them, but the lowered contrast (use of gray instead of white text in dialog boxes, removing colors from icons, below for example) is really silly bad, not good. Makes it harder, slower to use. Look at the join or order icons, the gray ones look so mushy. "Miter" value box in 2.0 is better though, so bonus points for that.

Well, I finally did a side by side comparison, seems like no difference w/ 2.0.

Don't fix what ain't broken. Here are some icons, 2.0 left 1.10 right. 1.10 is a lot more legible. In fact a lot of the interface looks to use light grey instead of white. This is not an improvement, it's going backwards. I will say, adding the "miter" label @ join in 2.0 is good. More of that please. But really, the light grey text & icons are bad, bad bad. Hard to read, those text bits are very small on a hi-res monitor.

And yes, V2.0 is very sluggish. Loads files into the raw engine very slowly. I'm not using a watch, but it feels like it takes 2.0 4x longer to load a 24mp nikon NEF than 1.10.

Well. 😒 Of course, you all un-checked hardware acceleration, right?

That's the question. Will 2.0 render my raw files differently than 1.10? on windows.

That's it. That's right. Ubiquitous format.

How are you making the selection for your cutout? Can you post a sample file that shows the situation?

Affinity should add "Disable OpenCL Acceleration" as a standard menu command. Except it should be disabled by default, and the Menu command should be "Enable OpenCL Acceleration" -->But then what would we talk about on the Windows Bugs Forum?