Joachim_L

My usual workflow for narrowing down problems in larger documents is to cut documents into half, then the half of the half and then the half of the half of the half and so on.

I don’t use this functionality much myself so every time I do try to use it I end up feeling like I’m having to learn it all again from scratch.
Specifically:
help not available – you can’t have both the Edit Table Format window and the Help window open at the same time (online help is available but, really?); unhelpful preview – the ‘preview’ doesn’t show what the table will look like, it only mimics parts of the formatting which is confusing (and the window is so large that it’s often difficult to see the table itself); counter-intuitive stuff – the add row button is to the right of the preview and the add column button is below; repetitive stuff – new cell formats are always copied from the first one, no way to specify which to use so much re-editing required; workflow-busting stuff – to change the text styles used you have to come out of the Edit Table Format window and go to the Text Styles, then edit, then go back into the Edit Table Format window – back and forth. And that’s just some of the major hassles. Lots of extra little niggles in there that stop it from being a pleasant experience.
Anyone with little Publisher experience trying to use this functionality early on must get very confused and, possibly, quite angry.

thats a shame  Thanks a lot for your quick response! @Joachim_L
Greets ✌️

Welcome to the Affinity forums @Dilly!
Hyphenation is a much requested feature in AD. The only two workarounds are a) do the hyphenation in AD yourself b) if you own APu as well, Edit in Publisher, enable hyphenation and Edit in Designer again.

Sounds like a good feature request, so this thread should be is already moved.

Sounds like a good feature request, so this thread should be is already moved.

Sounds like a good feature request, so this thread should be is already moved.

Closing an image with the X-Button always meant to me aborting / discarding of actions / changes and closing the window. In the Develop Persona it gets more complicated. If you want to close the window with the image you'll get the warning "The current file is being developed. Please complete or cancel before closing the document.". Then you have to press the OK-Button (Action 1), then press the Cancel-Button (Action 2), then press the Yes-Button (Action 3).
Pretty much action for simply closing a window and aborting everything in my opinion.

Problem solved! I found a setting "Hide extensions" and the library appeared. Everything is OK now, no more need for replies. Thanks once more!

Thank you very much my angel!! I am so sorry this is the first time for me

I guess this is covered elsewhere.
I made a few photographs of several different objects with the same lightings / conditions. In order to save me some time I made a new preset for the panels in the Develop Persona. Second time opening a RAW from the series of photographs there begins the boring repetitive work. Although the new preset is selected in the pulldown of the Preset (from processing last image) nothing happens. So I have to re-select the preset.
Maybe the presets can be part of the Develop Assistant? Second you can not save a preset over an existing preset with the same name, third you can not edit a preset, but this is not a real problem I think.

Unzip the attached file. Open the folder de_CH. Inside this folder there is maybe another folder called de_CH. Copy this (last) de_CH folder (with 3 files inside) to C:\ProgramData\Affinity\Common\1.0\Dictionaries (this is correct directory for additional dictionaries unless you changed the path). After copying, restart APublisher.
I tested this and it works.
Serif should really think about an easier way adding dictionaries. As this URL (https://github.com/LibreOffice/dictionaries) is recommended for additional dictionaries it shouldn't be too hard to install (as an Affinity function) from this place?
de_CH.zip

It is because one text HAS a white border. Select the text and have a look at the Stroke panel or the Character panel >> Decorations.

Yes, sorry this is what I meant and double-sorry, because I think carl123 has the correct solution.

Danke Joachim_L. Problem solved!

Closing an image with the X-Button always meant to me aborting / discarding of actions / changes and closing the window. In the Develop Persona it gets more complicated. If you want to close the window with the image you'll get the warning "The current file is being developed. Please complete or cancel before closing the document.". Then you have to press the OK-Button (Action 1), then press the Cancel-Button (Action 2), then press the Yes-Button (Action 3).
Pretty much action for simply closing a window and aborting everything in my opinion.

Thank you!

A minor point, but I do agree.
However, I can't reproduce on my macOS 10.14.6 with either Publisher 1.8.4 or beta 1.9.1.952. Maybe it is a windows bug, or perhaps there is something going on weird that it is document-specific.

Ok, simple error - btw made this too when I started with APu. Select your text starting with "This paragraph ..." and then have a closer look at the Character panel. There is a leading override set which makes no sense for what you want. Set this to "Auto" in your Text Style "Copy" (as well as for Headline - One) and you are good to go.
One last question: Why did you lift the baseline for all your text with 3pt? Personally I use lifting the baseline in rare cases and not for such basic text styles.

Amazing! Thank you so much Joachim!
I inherited the doc from an InDesign doc that was imported - so the choice wasn't actively made by me, but by previous author. I think the purpose of lifting the heading, at least, is to introduce a slightly less "aligned", slightly more "wild" look to the document, but why the Copy style was set to override the baseline grid I cannot explain, as the override is uniform.
I think what I need to do is reconstruct the document from scratch and then know, and feel comfortable, about each choice made, rather than navigating my way through it.
Once again, thank you so much for the rapid response. Haven't been a Affinity user for long, but I am slightly developing a crush on Publisher, Photo and Designer right now A super helpful community is obviously a key part of it, so thank you again for the warm welcome and help.

Appreciate the reply @Patrick Connor. @Joachim_L seems to be on to something about finessing the message delivered.
In the meantime, I'm going to cry into my cornflakes about how bad my GPU is

Don't get me wrong here, I would appreciate if working is done fast. Unfortunately this is not the case, a proof for this are the many bug reports regarding HWA. I do know that HWA is new to the Affinities and that bugs are not avoidable. With this in mind IMHO HWA should be turned off by default.
So asking here again: Where do I have a measurable benefit? I mean in which use case. Or do I have everywhere a benefit? I would love to see a benchmark image with a benchmark macro to compare HWA on and off.
My programming abilities are mediocre, but I could imagine that HWA should only kick in in certain actions and not all the time. Perhaps this is already the case? For my daily workflow I haven't experienced any noticeable benefit, so I turned it off to avoid problems.

Welcome to the Affinity forums @powcom!
As you already say, your graphics card seems to be old and does not meet the technical requirements. But you are right, the text should be written else like "Although your Windows version meets our requirements, your graphic card unfortunately does not".

Thank You friends. You saved me!!!

If you have all three installed and you use primarily APu, the assets of APu are also available in the other Personas.