adbosch

Doesn't work for me.

Does anybody have experience running the affinity suite on a Microsoft Surface Laptop Go 2 i5 / 8GB / 256GB? In theory there should be no problem, but how about in practice?

I cannot afford to loose my v1 files in v2. So please keep us informed in this thread. As soon as I get reassurance that my v1 magazines and books will open problemless in v2 I will transfer to the new version. But not before. Edit: I installed v2 and no problem importing my existing files. (win11home, surface laptop studio)

Let me rephrase my question: how should I adept or correct my previous hyperlinks so they will no longer lead to an error when exporting my document to digital pdf? What detail is it that causes this error in version 1.10 (and didn't in earlier versions)?

I still can't export to 'digital PDF', unless I remove all 'written' hyperlinks (those which I linked to an image do not seem to prevent export. Not even in the latest beta 1.10.211.56. Will this issue be solved soon?

Will there be a 1.8.2 official (not beta) release? I prefer not to work in beta.

I moved a crash causing afpub file to a location where it would't find the links. It opened normally (with dialogue about unfound links which I exited with a 'no' ) and I saved it with a new name. Copied this new afpub to the original directory and voilà: all cured. I don't know if this works for all but it's worth a try.

Tip(???): I created an empty afpub wich I called 'start.afpub'. Once open I can also open other afpubs which crash if I do noit have start.afpub opened.

I also have this problem. My files are relatively huge (magazines; too huge to share) and I do manage to repair them somehow, but it is evident that something is not ok with this new version (e.g. both version 1.7 as well as the latest beta 1.8 worked fine with my files). I have the impression that links (e.g. names without space???) and/or/in combi with preflight might cause the problem. I hope it will be solved (maybe I won't have to repair all previous issues:))

I can't get hyphenation in dutch to work. Please Affinity, instead of letting us guess what boxes to tick and where to tick them (I've had them all without any result) and other vague stuff (nl_NL, nl-NL, ??? why can't I simply indicate the location without obligatory but illogical directory names; I have 3 dutch files as per forum instructions, but are they still OK and why doesn't Affinity offer the 'without a doubt' working files). I need hyphenation in dutch badly and don't want to go back to Adobe. But I also cannot hyphenate by hand whole magazines (and correct endless errors afterwards with each slight layout change). This is important. Please propose a unambiguous howto including the support (files download).

When I use the text frame tool in APub to customize a particular text frame (e.g. add a border or set it to ignore text wrap, etc.), the next text frame I create will get the same settings as this customized text frame (gets a border or ignores text wrap, etc.) whereas this is absolutely not what I want. Is it on purpose that the text frame tool keeps applying its settings to all new text frames? (it took me some time to figure out why wrapping text didn't work until I found out that somewhere earlier I had it set off in the text frame tool. In my publication I now have a serious number of text frames not responding to wrapping whereas I intended it for just one or two instances)

I sometimes have to transfer my Designer file to a colleague working only in Illustrator. So I create a SVG. But when opened in Illustrator it appears to have different values (see images attached: to the keft my original file made in Designer, to the right what I get when I open my SVG in Illustrator; dotted lines in Designer have been replaced by one giant dot in Illustrator; and look at the difference in size). What do I do wrong? Shouldn't SVG-files be identical indendant on the program that usees them? HipHopBoekleggerAlt.svg

I disabled the startup panel in Photo. And regret it. Is there a way to get it back?