TheOtherRoland

Do you promise? I've had my heart broken before like this.

Discovering this bug was an unexpected Xmas present that I now wish to return.

Hello. You'll probably have better luck getting an answer to your question by starting a new topic of discussion; this thread is just for the unofficial PDF manual. I'm sure the mods can assist to move this over.

I can't upload the file because it's a manuscript for a soon to be published book. So that's not an option. But if no one else has this problem then it must be anomaly. For now, I'm doing my workaround. It may help to note that my index is in a separate master file at the end of the doc. that other text does not flow into. Not sure if that matters, but there are many sections. Either way, the crash is totally consistent. If the index has been created, then I can't add topics to it. As soon as I remove it, I can add topics.

I've had the same issues on two different macs using both APub 1 & Apub 2. The only way I can get a topic into the index list is to delete the index itself and then recreate it afterwards, otherwise I get the spinning wheel of doom — never stops. I have to force a quit. It could be file related. Or not. I have a book template file so that might be one source of the issue. Someone else must surely have this issue?

I was working outside of Apub 2 for a while and returned to it today. When I tried to add an index topic to an existing index (for a 250 page book file), Apub 2 crashed repeatedly each time I tried to add a topic. I then remembered my previous work around, which was to delete the index before adding any topics to it. (Not exactly intuitive) When I delete the index (highlight text and delete) I can then add topics as expected. However, I can't see them as entries on that page until I do the "insert index" command. But at least it works for now. But if I was a programmer — which I'm not — this is where I'd be looking for the source of the bug that obviously exists. System and technical considerations: I'm using Monterey on an old Mac Pro. It is sunny outside. I am drinking tea (Red Rose).

In the meantime, it looks like I have some merging to do.

I had Pub v2 regularly crashing while working on a 20 chapter book and trying to add an index topic. Not a marker in a document; just a topic without a reference link. The way that I solved this issue was by removing the index text from the text field itself and then adding the topics. After that, I used the "insert index" command to put a new index in place. Clearly something is wonky, but not a terminal joy killer. This is on a Mac, Monterey Intel. The Index issue that MikeTO brought up is haunting me too ie. no master index for the book. No way to search 20 chapters at once for a topic when they are split into separate docs. Ugh. I used one doc. in a previous book. Much easier to deal with, but makes the book feature seem kind of useless.

Very cool. Thank you. Downloading now. Just reading your manual re; books. This is excellent. It digs into issues that would not be talked about in the company manual — such as why using the split feature in books is not a good idea; which I'm learning for myself right now. Thanks again.

I have no idea how big the manual would be for Publisher. But I also use audio apps such as Cubase and Digital Performer, which have traditionally had very large pdf manuals. I think from a user's perspective the manual size is not an issue, but from the coding/creation side, I can understand why silent online updates are a preferable setup. Saves time and is easier to organize. Totally agree.

Yes, for the price of a small car...you can now own your very own manual. I'm just joking around. But on a rare serious note: Blender offers a web-based version of their manual but also an ebook version — the core of which is html; I know because I create my own ebooks as well. I'm just saying, I shouldn't have to "McGyver" something from 3rd party software just to get an independent users manual for Affinity stuff. As I've said, I've used the in-app help menu in the past and it's been helpful. But even that is tethered to the app itself, whereas PDFs (and ebooks) are "free range."

Thanks Mike. But my initial grumble fest was about having to be online for that information — whereas a PDF gives you a little freedom from being tethered to the modem. The in-app help for APub is okay. Not as good as a PDF though because you have a number of options, including "+" in the menu. If I could have the ONLINE version of the manual as a PDF (not as single printed pages as they offer) then I'd be happy with that. Can't be too hard to make that happen, can it?

I just gave it a second look — that "thing" you spoke of in the help menu with the tiny font in the TOC. It's okay I suppose. If I press command + on my Mac, I can get the font to enlarge enough to read; my eyes aren't what they used to be in terms of reading small print these days. [Note to self: get an eye transplant.] I just upgraded to v2, so it's more like a knee jerk reflex thing: "I need a manual." And then I start reading the help files and realize 1/2 the stuff I need to know isn't there anyway. (Manuals have a habit of not going into forensic detail.) Okay, enough of this silliness. Back to work.

No can do. I've noticed a spike in my backup generator when clicking on that link. (It's drawing too much power from the di-lithium crystals, captain!) Okay, jokes aside, I've probably used that feature on a number of occasions — in addition to online tuts, etc. — but I guess I'm spoiled with always having had a nice large, picture laden PDF file to stare at in most other apps. Perhaps using the traditional bribe system will get them onboard. I'll start with an offer of $3.00 (CDN, not USD).

Hello, fellow Affinitizens. I've been using Affinity products since the early 1900's and don't recall there being a PDF manual. I know there's an online manual. But what if there's an apocalypse and all the electricity goes out? What then, huh, Mr. Smarty Pants? I'm not that lost for answers, but I'm curious if anyone has [NO!] made any efforts to [NO!] make a [NO!] ... oh, never mind. Just having some fun with this information super highway thing. But I'm curious, is this an evil ploy to get us buying that print edition book; you know, the one that costs as much as a small car? Is there a secret Affinity cabal behind keeping information in pdf form out of our hands? Perhaps someone can run with this as an idea for a new novel? (Just mention me in the dedication).

Thanks, Oufti. I have my own book template that I use now to avoid those earlier hardships. But I haven't tried to revisit that process yet. I attribute it to PTSD.

Just upgraded. Now it's too late to turn back. Your devious marketing tricks have worked to win me over. Now...must...keep...moving...forward...[face plants into hot desert soil]

Wow, that was fast. Glad to see new things arriving. I just upgraded yesterday so I'm looking forward to an even brighter future for apps that are already doing most of what I need. Thanks, Affinity team.

Just going by memory, it was a text styles issue where the text style was being lost in the TOC text when the reset or recreate TOC was clicked. Maybe someone who dealt with this issue before will also see my post and help confirm. I found a work around, so it didn't bother me afterwards too much. No pressing urgency to update. I've seen a few crash reports that make me nervous.

Hi folks. This is just a generic question for anyone publishing books: how is the TOC functionality in Publisher version 2 software? I know that a few of us were having a discussion during the v1 days to come up with a work-around for the font family and style always changing with each new update to the TOC. Does this still happen? Any other issues? I haven't upgraded to v2 yet and am looking for perks to make me move beyond v1 — which is working perfectly fine for my needs atm.

Thanks. Keep those font issues coming.

Thanks, Dave. I think it would be helpful for a guy of your skill set to contribute to the betterment of these apps. If I was doing this, I'd probably use this thread to post those findings — just to keep everything under one roof, so to speak. But I see you've already made a separate thread, so I guess that'll be the approach. Regardless, I'm sure the devs will be taking notes and maybe even contacting you privately to get some feedback. They seem open to a lot of our input and surely they will want to fix any font glitches that exist in version 2.

He did say " If you have a backup of those Assets," so I guess he's assuming that you did make a backup before you pressed clear.

(I didn't read all the posts but I'll just put this here, in case it helps any) I had to deal with this issue in v1 (I still haven't updated yet but I think it's applicable). When you set up master pages, also set up single page masters for Left and Right (or "verso/recto" for those who don't speak English ) so that you can drop them on a spread individually to reorient the page. You then have to realign the content to the margins - depending on what you're presenting and what the inset is. I'm just going off memory from a year ago.  Hope my memories serves me recto.

Thanks, Daniel, for helping to identify the cause of the problem. This should make it easier for the coders to codify. (See what I did there? )