Jump to content

PatrickOfLondon

Members
  • Content count

    47
  • Joined

  • Last visited

About PatrickOfLondon

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    : London, England
  • Interests
    Technology per se, during all of my seven decades

Recent Profile Visitors

322 profile views
  1. I wonder if this is related to the problem I found....
  2. PatrickOfLondon

    Table cell height problem

    I had done a resizing operation like that, prior to its going haywire. In line with your suggestion, in the attached document, after scrolling down a very long way I did get hold of the resizing handle and pull it back up onto the page. But in the Table panel, Cell section, Height box, the number shown was still absurdly large. When I tried to type in a sensible value, and then pressed return, the value I entered didn't set. Instead, the value increased to some new random figure, so it does seem to be some problem or bug in the mechanism that handles cell-height entry (either manually-by-typing-in, or by scrolling the mouse wheel within the "Height:" box).
  3. Hi, I'm using Affinity Publisher 1.7.1.404 and have encountered a strange, table cell height problem. I was adjusting cell height when the value suddenly changed to an insane number. It now seems impossible to reset the cell height to any sensible value. It has taken on a mind of its own. A sample document is attached. If it is opened in the latest beta version, 1.7.2.420, the behaviour is still the same, as reported on the beta forum: Looks like a bug in the cell-height value-adjustment mechanism....? table rogue behaviour.afpub
  4. Hi, I'm using Affinity Publisher Beta 1.7.2.420 and have encountered a strange, table cell height problem. I was adjusting cell height when the value suddenly changed to an insane number. It now seems impossible to reset the cell height to any sensible value. It has taken on a mind of its own. A sample document is attached. If it is opened in the retail version, 1.7.1.404, the behaviour is still the same. Looks like a bug in the cell-height value-adjustment mechanism....? table rogue behaviour.afpub
  5. Thanks Old Bruce, and glad to be of help. Having worked it out (finally) I wanted to share it with anyone interested.
  6. Some more material that might, hopefully, help someone, somewhere. The image attached was produced from the spreadsheet also attached, both of which seek to explain. Page and Section field numbering tests 2019-06-24.afpub Affinity Publisher Page numbering and Sections.xlsx
  7. Thomas, ich danke ebenfalls, and misunderstandings happen on all sides when we are all trying to understand something (Affinity Publisher 1.7.1.404) that's new and still relatively unfamiliar, and also, in some places, not particularly well signposted, by Help or in-studio item-naming. I've been trying to explore it further, and discover how it works in this area. It seems to me that "Run" means "continuous, non-restarted, page numbering sequence". I'm hoping that the attached image and sample document might possibly help anyone else who is as confused as I was (and maybe still am) in trying to understand this. Page and Section field numbering tests 2019-06-23.afpub
  8. Thomas, Referring back to the thread title, the field I was investigating was the Total Pages field. It remains true, I believe, that there is no way to alter the format for that. Your contribution and others' contributions have pointed out a way to report the overall page-count by using other, number-format-alterable fields, which is helpful, but unrelated to the Total Pages field, which was the subject of the thread. In relation to the lack of a field for counting section pages, the "so what?" point is that it can often be useful in a document to report the number of pages within a section. The subject of reporting that was raised by another contributor, and it is relevant to the general concept of using fields to report document page-counts in various different contexts. A "section page-count" field might therefore be a useful addition to future, iterative releases of Affinity Publisher, but I endorse your suggestion that none of the other things you mention would be.
  9. Update 2019-06-24: Please note this post reflects my earlier misunderstanding of how the fields work. It's been left here to serve as an archival record, but I have subsequently annotated it, in mauve. See my subsequent post for a hopefully more accurate understanding and explanation. Thanks to all for offering thoughts. I played with Thomas's sample document and, to develop his comments a little bit further, field: Document Sections, Page Number # means absolute (no, it's relative to the section-originated page numbering sequence) page number within the publication; (no, it's within its section-originated page numbering sequence) obeys the number-format for the section field: Document Sections, Last Page <Last Page In Section> means absolute (no, it's relative to the section) page number (within the publication) (no, it's within the section-originated page numbering sequence) of the page at the end of this section; obeys the number-format for the section field: Document Sections, Run Last Page <Last Page In Run> means absolute (no, it's relative to the section-originated page numbering sequence) page number (within the publication) (no, it's within the page-numbering sequence) of the last page in the print-run, = document page-count; (no, it's the last page number assigned by the corresponding page-numbering sequence) obeys the number-format for the section field: Document Statistics, Total Pages means document page-count; does not obey the number-format for the section and cannot be formatted as Roman numbers, alphabetic, etc. There is apparently no field for reporting a section's page-count. (but if a section has its own unique page-numbering sequence, that can be used for this purpose).
  10. Hi, Although I can format the Page Number field as i, ii, iii, iv, etc using the Section Manager from the Pages studio, there doesn't seem to be any way of setting a matching format for the Total Pages field (page-count). Please see the attached picture. Have I overlooked something? Thanks in anticipation, for any solutions suggested.
  11. PatrickOfLondon

    Footnotes/Endnotes

    I can certainly appreciate the frustration, from people who need footnotes and endnotes, about their non-availability in Affinity Publisher at present. I'd really like to see these features too. However, I feel confident that they will appear, in the not-too-distant future, in an incremental version along the way. And there are alternative products I can use, if I absolutely must have endnotes and footnotes right now. I'd like to add my thanks to all at Affinity / Serif for offering the marketplace this choice of products, at their price-point, alongside currently perhaps more feature-rich, but certainly much more expensive products from other companies. Given that AfPub is currently on sale for a one-off price of 3.9 months' worth of a single-app Adobe subscription, I'm personally very happy with the value I'm getting at present, and hope to see enhancements in the future of the kind we've seen in the other Affinity products' evolution since launch.
  12. PatrickOfLondon

    Pencil tool whereabouts

    I apologise if I'm overlooking something, but although Affinity Publisher Help mentions a Pencil tool, it seems to be absent, as illustrated in the accompanying image.
  13. PatrickOfLondon

    Tiny corrections to "View > Customise Tools..."

    Thank you Alfred, for unearthing the not-quite-so-missing Affinity Cat. In which case, I think there's a correction required to the Help entry for Cat, which says the Alt key is used.... but it's the Shift key that's required, instead. Hoping a separator tool-tip will make it into the release version (for which things are now looking very good), or an early update to that.
  14. Aiming for perfection: missing tool-tip (and missing cat...) -- please see attached image.
  15. Hi, apologies for reporting such a minuscule error, but speaking as a perfectionist.... in Help > Appendix > Preferences > ... Filler Text • Instead of placeholder 'latin' text you can add our own custom text content (any language) to act as filler text. ..."our" should be "your". You could also helpfully add "in" before "any", and capitalise "latin", so the corrected help entry would become: Filler Text • Instead of placeholder 'Latin' text you can add your own custom text content (in any language) to act as filler text. At least it's something that's easy to fix!
×