fde101

Serif has clearly answered earlier in this thread that this is being actively worked on but it simply is not ready yet.

Paragraph Decorations will work for that, too. Here's a quick example with a top and bottom line around several paragaphs. (Very quick/dirty; obviously some more tailoring of the line position is needed.)

 

Serif has clearly answered earlier in this thread that this is being actively worked on but it simply is not ready yet.

I should have mentioned that if you want to use this and really want A...Z section headings, just add those manually as your final step before publication. At least the hard part, the indexation, will already be done.
I know there's already a workaround for cross references but I really hate the idea of all those extra text objects in my document. Here's another option but since this is manual you'd only want to generate the cross ref page numbers once before publication.
Add your cross ref destinations or anchors as index markers using something consistent for parent topic - I suggest "x". The actual index topics should be meaningful to you but also very short. So I might enter "Smith" as the index topic and "x" as the parent topic. To add a cross reference to the "Smith" destination or anchor, I'd enter "xSmith" in plain text - it's somewhat important that these text strings not be much wider than the width of the expected page numbers or you could have an unexpected line break change later. So I might use "xSmi" instead. Just before publication, I'd generate the index and cut out the "x" topic section which would be something like this: xJone     78
xOwe    117
xSmit    231
xWill       82
And now I'd manually find and replace the text strings with the page numbers. The advantage of this approach is you'll have accurate cross references far easier than doing it manually but the downsides are it's a big pain, proofreading would be more difficult, and you can only do it once, because once it's done you can't find the outdated page numbers to update them. But if you want think you might need to repeat this, just format the cross references (i.e., xSmit") with a character style named Cross Reference. This style wouldn't need to have any attributes because then even after changing xSmit to 231 you could find all the cross references later by searching for the style name. You wouldn't immediately know that 231 had been xSmit but you should be able to get that quickly from context and look it up in your index table. Crude but it would work.
I'm actually going to do it in a simpler but more manual way since I only have dozens and not hundreds of cross references. I'm using Insert Anchor to insert an anchor named "Smith" and then the same command to insert a cross reference named "gotoSmith". Then when I want to update my cross ref page numbers, I simply use the Anchors panel to display each page with anchor, i.e., page 231 for the Smith anchor, and then I display the matching cross ref anchor page, i.e., gotoSmith, and type 231 after the anchor.
If we had scripting and if the necessary parts of the object model were exposed, it would be easy to automate this. The script would loop through each anchor in the anchors collection and if it was prefixed with "goto" the script would get the page number of the matching anchor that wasn't prefixed with "goto", and insert that page number to the right of the goto anchor, deleting any existing numbers before the next space. But of course I'd just prefer an Insert Cross Reference command. 🙂 
Using two linked frames would work if the index "names" (parent topics) were what you wanted readers to see and you were okay with them being alpha sorted (an index named "Index" would appear before an index named "Sculpture Index"). It would be easier to just manually insert a column or page break between them rather than fiddle with the text frame same though.
And yes a TOC would work better for a table of figures in most cases. The challenge is the TOC uses all of the text in the paragraph and you might prefer something shorter. So if the caption on the figure is "Figure 12 - Population Trends in Midwestern Missouri, 1812–1912, R.B. Williamson and S.K. Rawlinson (1938, Winston University Press)", that entire paragraph would be in the table of figures. An index is more flexible for this.

Not only does this thread violate the guideline of only one feature request per thread, but it contains also several duplicate requests which have already been discussed at some length.  Please search for existing discussions before adding threads, to avoid duplicating them.
 
See the guidelines on posting feature requests at the top of this page: https://forum.affinity.serif.com/index.php?/forum/52-feature-requests-suggestions/

Are you kidding?  It is 2022 already and NONE of the Affinity products have implemented a telepathic remote control for the speed of the fans inside of microwave ovens...  SERIOUSLY?
 
For you it is multi-page spreads.  For some it is right-to-left language support, or footnotes and endnotes, or cross-references, or the ability to make editable PDFs or various eBook formats, vector mesh warp, support for variable/color fonts, or more highly compressed raster export formats for use on web sites...
 
First off, these are feature REQUESTS - we are asking for them - that does not mean that Serif is under any obligation to implement any of them, ever.
 
Serif has been gradually implementing things that people are asking for, but they do need to prioritize and they may not always even agree with some of what people are asking for.  Some features simply take time to implement and they can't do it all at once.  There were comments in other threads already that they have tried to bring more developers on board to help speed some of these things up but that they have a hard time finding qualified people where they are located.

Are you kidding?  It is 2022 already and NONE of the Affinity products have implemented a telepathic remote control for the speed of the fans inside of microwave ovens...  SERIOUSLY?
 
For you it is multi-page spreads.  For some it is right-to-left language support, or footnotes and endnotes, or cross-references, or the ability to make editable PDFs or various eBook formats, vector mesh warp, support for variable/color fonts, or more highly compressed raster export formats for use on web sites...
 
First off, these are feature REQUESTS - we are asking for them - that does not mean that Serif is under any obligation to implement any of them, ever.
 
Serif has been gradually implementing things that people are asking for, but they do need to prioritize and they may not always even agree with some of what people are asking for.  Some features simply take time to implement and they can't do it all at once.  There were comments in other threads already that they have tried to bring more developers on board to help speed some of these things up but that they have a hard time finding qualified people where they are located.

Are you kidding?  It is 2022 already and NONE of the Affinity products have implemented a telepathic remote control for the speed of the fans inside of microwave ovens...  SERIOUSLY?
 
For you it is multi-page spreads.  For some it is right-to-left language support, or footnotes and endnotes, or cross-references, or the ability to make editable PDFs or various eBook formats, vector mesh warp, support for variable/color fonts, or more highly compressed raster export formats for use on web sites...
 
First off, these are feature REQUESTS - we are asking for them - that does not mean that Serif is under any obligation to implement any of them, ever.
 
Serif has been gradually implementing things that people are asking for, but they do need to prioritize and they may not always even agree with some of what people are asking for.  Some features simply take time to implement and they can't do it all at once.  There were comments in other threads already that they have tried to bring more developers on board to help speed some of these things up but that they have a hard time finding qualified people where they are located.

Are you kidding?  It is 2022 already and NONE of the Affinity products have implemented a telepathic remote control for the speed of the fans inside of microwave ovens...  SERIOUSLY?
 
For you it is multi-page spreads.  For some it is right-to-left language support, or footnotes and endnotes, or cross-references, or the ability to make editable PDFs or various eBook formats, vector mesh warp, support for variable/color fonts, or more highly compressed raster export formats for use on web sites...
 
First off, these are feature REQUESTS - we are asking for them - that does not mean that Serif is under any obligation to implement any of them, ever.
 
Serif has been gradually implementing things that people are asking for, but they do need to prioritize and they may not always even agree with some of what people are asking for.  Some features simply take time to implement and they can't do it all at once.  There were comments in other threads already that they have tried to bring more developers on board to help speed some of these things up but that they have a hard time finding qualified people where they are located.

Are you kidding?  It is 2022 already and NONE of the Affinity products have implemented a telepathic remote control for the speed of the fans inside of microwave ovens...  SERIOUSLY?
 
For you it is multi-page spreads.  For some it is right-to-left language support, or footnotes and endnotes, or cross-references, or the ability to make editable PDFs or various eBook formats, vector mesh warp, support for variable/color fonts, or more highly compressed raster export formats for use on web sites...
 
First off, these are feature REQUESTS - we are asking for them - that does not mean that Serif is under any obligation to implement any of them, ever.
 
Serif has been gradually implementing things that people are asking for, but they do need to prioritize and they may not always even agree with some of what people are asking for.  Some features simply take time to implement and they can't do it all at once.  There were comments in other threads already that they have tried to bring more developers on board to help speed some of these things up but that they have a hard time finding qualified people where they are located.

Go into Preferences within Affinity Photo and make sure the Enable "Save" over imported PSD files option is checked.

There *is* a "full screen mode" on the Mac, but it is an *actual* full-screen mode which hides the menu bar, title bar and dock along with any other applications to let you focus in on just that one.  Bumping the mouse against the top of the screen shows the menu bar and title bar temporarily.
The traditional Mac feature which corresponds to the Windows "maximize" behavior is called "Zoom".  Go back to before the full screen mode was added and the green button on the tile bar would trigger the zoom behavior; it still does for windows which do not support full screen mode (as is determined by the individual applications - some support it, others do not).  Now that full screen mode is available, if the window supports it, the green button activates full screen mode; holding down the option key while clicking on it gives you zoom instead.
In contrast to the maximize feature on Windows, which makes the window consume the entire screen regardless of content size, the zoom feature on the Mac essentially means to make the window as large as it needs to be to show the entire content, up to the limit of the size of the screen - so if the entire content of the window fits in a space which is only half the size of the screen, that is how large the window is supposed to become.
 
They actually do support the standard OS-provided full-screen mode on the Mac, as I described it above.

I actually find the current behavior of the export dialog (defaulting to the last folder I exported something to) MUCH more helpful for the projects I've used it with than the behavior requested here would be.  I agree that the behavior you are suggesting would be nice for "Save As", but I would much rather that "Export" be left alone (or at a minimum provide a preference to keep the current behavior).

Unbelievable but true: just now, in 2022, I have received an InDesign file where footnotes are still formatted by hand, in frames created for that purpose!

Not just "old" bibles - and it should be noted that these techniques are frequently used together.  The "mediannotes" as you are referring to them are commonly used for cross-references to other related verses while footnotes are used to present commentary and/or notes from the translators related to how the translation relates to the original-language text, etc.  As a result, this highlights a need to support multiple "streams" of notes of different types presented simultaneously within the same story.

Not just "old" bibles - and it should be noted that these techniques are frequently used together.  The "mediannotes" as you are referring to them are commonly used for cross-references to other related verses while footnotes are used to present commentary and/or notes from the translators related to how the translation relates to the original-language text, etc.  As a result, this highlights a need to support multiple "streams" of notes of different types presented simultaneously within the same story.

You don't need symbols for that, the Assets panel is likely a better fit, and that one is available in Photo.
Unfortunately they do not sync among the apps - each of them has its own assets library - but the feature is there in all three, and you can export assets from one app and import them into the others.

@fde101 No, I've never intentionally used overprint settings in Affinity Designer.

True, but in this case the OP is round-tripping between Capture One and Affinity Photo, which is exactly the situation that feature was designed for.  Capture One is no more likely to produce a PSD file with those functions than is Affinity Photo.
That said, it is a fair point that any text which may be added in Affinity Photo becomes rasterized in the PSD (C1 can't add text to the photo so it wouldn't be coming from there).
I just tested to see if TIFF also did this, and I found that when I opened a TIFF from C1 in AP, it not only allowed me to save over the existing TIFF (and did in fact keep the .tif extension causing me to question the original request as it seems to work just fine already?  Maybe this is a Mac vs. Windows thing - it works fine already on the Mac but the Windows version is changing it to .tiff upon save?) but also gave me the option to save with the Affinity layers intact in the TIFF, which does preserve the text as editable, an option which is not provided for PSD.

I'm really enjoying this epic metaphor battle. Carry on.

I would like to add vertical gradients to text which goes over multiple lines, with the gradient being "reset", so to speak, with each new line, so that every line is basically treated separately.

Note that you can also leave it set to Inherit for the existing layers, but group them, and set it once on the group - the layers within the group will then "inherit" the setting from the group.

Note that you can also leave it set to Inherit for the existing layers, but group them, and set it once on the group - the layers within the group will then "inherit" the setting from the group.

Serif has made it quite clear it will be some time before this feature shows up.  Why you would have "waited" for it "in each release" is beyond me.
 
They have said repeatedly that they do want to add it.  No one ever said that they can't.  It just is not a high priority right now and they are working on other things instead.
 
It is not essential to me.  I never produce documents in multiple languages myself, so I have no use for it whatsoever.  I certainly see the value of being able to work in multiple languages, as many people do need that, and the possibility exists that I may one day have a use case for it (and thus I am interested in seeing this happen, though it is not nearly as high a priority as numerous other things that other people are similarly complaining about the lack of - cross-references for example are among the biggest ones for me, as are tables that span multiple pages; I also would like to see global layers added sooner than later).
As others have also stated, this is something that clearly takes time to get right, and that is time Serif could be spending on other features that are much more essential to many people, and which they can get in place much more quickly than they could offer this.

I have a Wacom tablet.  I never use precision mode.