rubs

Uploaded.

Previously the beta versions were clearly marked, not sure when the developers changed it.

I think the Export Persona is a great idea. It's meant to automate repetitive tasks such as deciding which slices to export, naming them and remember your settings, among others. (It was one of my deciding factors when I moved from Xara to Affinity Designer.) I don't see multi-page PDFs would conflict with the existing options. To me it's still an omission, and a quite easy one to solve to begin with. Judging for the many topics regarding the subject to date, others seem so think the same way.

So... after all this time and many betas, exporting as a multipage PDF from the Export persona still doesn't work. It's just a matter of adding a checkbox, the functionality already exists in the Export PDF dialog. Exporting manually every time is cumbersome.

When opening a recent file, I got the following "Your file has errors. It was possible to open it, but you are advised to take a copy of this file and report this error". Is there a way to find out what kind of error is this, and where its it? Is there something missing? The error appears in both Affinity Designer 1.7.0.367 and 1.7.1.404 beta. Thanks in advance.

Sorry, this quote is from the 1.7.1.385 Customer Beta changelog. I didn't understand why Designer would have page navigation, but @Mark Ingram explained it.

Huh? Does Affinity Designer work with pages at all? I'm pretty sure I missed this.

This seems to get worse immediately after making a copy of an existing artboard using Ctrl+Drag. (BTW doing this became unbelievably slow in the latest versions.)

Another very old, strange problem that's still present in 1.7.0.367: The keyboard doesn't work in the Layers panel. After waiting about 15-20 seconds it works again.

Possibly fixed in the latest version! Too bad the search is case-sensitive now, I hope you fix it soon. But thanks a lot for the improvement.

The procedure below should work: Close any running versions of Affinity Designer. Better yet, close anything Affinity. Very important: backup all files in %appdata%\Affinity\Designer\1.0 in case something goes wrong. Copy all files from %appdata%\Affinity\Designer\1.0 (Beta) to %appdata%\Affinity\Designer\1.0. I'm not sure I've mentioned it before, but please backup your files first, just to be safe.

Good to know that, much needed. But please make it case-insensitive again, otherwise we won't be able to find our assets. Thanks for answering.

In version 367 RC2 (I'm not sure about previous ones) it seems that Assets search is case-sensitive now. I have an asset called "Balloon", but when I looked for "bal" it didn't return anything. "Bal" worked. I hope this is not intentional!

Sure, that's what worries me. Another release and most old problems are still there. Oh, certainly not. To quote a friend, only obsolete software isn't buggy I refer to those "old time favorites", things that just don't work as expected for years. You know, the ones you've never fixed and are not answered by Serif. Some of them, from the top of my head: Complex boolean operations Constraints (lots of issues with those) Expand stroke Selecting then moving several artboards Symbols Objects moving inexpectedly when grouped / ungrouped Continuous export Sluggish search in assets 1980's style text tabs UI Performance problems in the Windows version And so many more...

What bothers me everytime I see those little RC's appended to the version numbers is that all the old bugs and problems from years ago are still being ignored. (Shouldn't we call them "classic" already?) Oh well...

Yes, this is an old bug. One of several regarding constraints. Never solved.

I believe this is an undocumented change in AD Beta. AFAIK this was already there, I've already observed this behavior. I didn't install beta 331 yet.

Right! That's probably because Windows is in pt-br and Affinity Designer is set to en-us. (Serif's Portuguese translations are quite bad.)

That's Portuguese for "name" -- not so different

Great, thanks!

Thanks for your answer, now I understand what's happening. Unfortunately this particular file is subject to an NDA, so it cannot be shared with other people. Anyway agree with you, this message shouldn't even exist!

When opening some files from a coworker I get the following: If I click Yes, I get an Open dialog with the following option: This would make sense for Affinity Publisher, but Designer is the only app we have and use here. Since AD doesn't even have a resource manager, how can I even know which is the name of the missing resource(s)? Aren't all resources in AD embedded? I don't think there is anything missing from the file, so why the question? How can I make it go away? I'm confused... Please advise, thanks!

The fact that the measuring guides for artboards never worked as for others objects (Ctrl key does nothing) makes it even worse.

It was always easy to inadvertedly misalign artboards and get blurred results on export. This is now easier than ever. Please go back to what it was before.

Oops, spoke before checking out a large asset collection. Nope, the search performance is still sluggish, e.g. in the Material Design Icons collection.