Search the Community
Showing results for tags 'header'.
We may have discrete Sections available as Fields but running footers/headers making use of specific paragraph types (i.e. Heading 1, which might have Flow break to the top of the next page). Ideally, we could configure which paragraph styles are accessible in View > Studio > Fields. My suggestion would be to have it user-configurable from right-click the "Edit <Paragraph Style>" Paragraph > Field Options Available as Field? First or last available? On Page or Spread? (see relevance of first/last in previous question) This would make for some really robust footer/headers on master pages, esp. in education or technical materials with dense, structure order to their contents, allowing us to guide the read through. The Field referencing the other Paragraph style occurring in the main document could be styled by any existing paragraph style as expected.
When I add a table to my document it never shows the column headers (A, B, C, D, . . . ) or the row numbers (1, 2, 3, 4, . . . ). I can't seem to find a setting to show or hide them. I am running Publisher v 188.8.131.52. I am running Mac OS Mojave.
In the past I (and others reported) had some corrupted files, especially I had for example a crash at program start because of a corrupted AppData-Affinity-Folder, that later turned out to be a corrupt assets.propcol file. I don't have the broken files any longer, but I was thinking about a way of recovering data out of such corrupt files. Is there already a tool or command line switch or other way to try to recover such files? If I think I would manage all my assets and brushes in those files and out of a sudden it get's unusable for the Affinity program, I would go crazy. It would be good to have a tool that could try to read the file and try to recover as much as it could and write a new file with all that could be recovered (keeping and not writing to the corrupt file of course). Maybe rewriting header or stuff like that, or if it can't detect the file from the file itself, that someone can say, hey this was an assets.propcol file for example and then it tries to recreate it.