Gianni Becattini
Members-
Posts
364 -
Joined
-
Last visited
Everything posted by Gianni Becattini
-
Table cell margins
Gianni Becattini replied to Gianni Becattini's topic in Affinity on Desktop Questions (macOS and Windows)
It works, thanks! -
Table cell margins
Gianni Becattini replied to Gianni Becattini's topic in Affinity on Desktop Questions (macOS and Windows)
-
Congratulations, Walt, you won! Almost every chapter developed a second section with "start from page" option. Don't ask me why, certainly I didn't create them. But having removed them, things seem again in the right direction. By the way, I believe I find often chapters which changed from "continue numbering" to "start from". But the important is that I am again in the race... thanks!
-
This is the window of Apub. Note the page numbers: 427, 428 (not shown), 429, 430: This is the produced pdf file. Note that we jump to 437 without any visible reason. This seems to happen without a logic. Page numbers seem to jump backward and forward, even from an export to another. Is it my fault or a bug?
-
In addition: if you clear the target style and then apply it again nothing changes (KO) if you just delete not the text frame but just the text and then you type it in again, it often works OK the CR naming behavior is very strange; see the attachment. Sometimes it include the text after the dash, other times it doesn't - the naming seems to be connected with the problem. If you get a wrong name, it is a sign that something will go wrong. In my cases, it got often the name of another CR. I tried also to delete the pointed text AND the CR. Often, when you try to re-create a new one, the old name is retained even if you change completely the text. In other words, it seems that when you create the CR, some hidden info is retained in the pointed text frame, where probably the problem is. another bad sign is when you get no chapter number in the table in conclusion, to be safe, when you have problems like these, it is better to delete the destination text frame and create it again. In this way I never had problems again (until now 😁). I have verified more times what I said.
-
I believe I found something... I created a new file with just my TOC: same problem I added a true TOC: it worked OK Eventually I discovered that the wrong information is in the referenced paragraph (Main Section Title in my case). Deleting them and creating new ones, the cross-references return to work. But why have they got damaged? And why the "true-TOC" can see them correctly? A reference should be a reference....
-
Some information, don't know how useful. I created a brand new book (by the way: it is very annoying that as default APub sets "start from page number" for each chapter instead of "continue numbering". I could not find a way to set them all, you must go along with each of them). I did not add the "500-Series" chapter, but... even destroying all the references and creating new ones, again appears always the "500-Series" cross reference. So the wrong information must be stored in the other chapters. Perhaps the first one with my pseudo-TOC?
-
In (1) you can see the current situation. On the left you see the book and in the page there is something like a hand-crafted TOC. On the left, you can see the C-R list. Until yesterday, they were all OK. Now the ? says that they cannot be found. I already noted that the Name is often wrong, but the page number is however OK. In (2) you see the target page (the paragraph "The 300-Series" in Main Section Title style: In (4) I open the C-R in Edit In (5) I deleted the C-R and try to build a new one, like it was before. Surprise! The new C-R says "Page 12" instead of "Page 96", as it was expected, and also the C-R name is wrong (both are from another chapter, that in addition is currently closed). Or I made another mistake inside my mistake, or it is another bug inside a bug, I believe... (not ironic, really asking). I add another post following this....
-
Thanks, but having many different pages with many text layers it would be unpractical to add a layer only for this. Perhaps I could have relied more on master pages, but, on the contrary, today I am removing them, which created more problems to me than solved (probably because I misused them, but not only, I believe). Thanks however.
-
Yesterday was terrible for me and for more than 40 times I had to kill the stuck Affinity Publisher (mainly when I synced settings or cross references across a book). But I strongly believe that this time AP is only partially guilty, or completely innocent. The Public Danger N.1 is, in this case iCloud Drive. First: it made a sync error that I am not able to explain. I closed my work at office, switched my home computer on, waited to be sure that the sync was completed and noted some strange behaviour in the file dates/times. I checked tho other computer, noting that it had not finished the sync. I waited, and I could see the new files to be synced to the old date. 6 work hours lost. I am sure I made no mistakes (no save) but it happened. However, I think it is only a sporadic event, and this is not my caveat here. Second: I could understand that, when you have less free space on your HD (120G in my case), iCloud starts to "optimise" a lot of files, removing them from the disk and leaving them in the cloud. It should do that with files that are not accessed since long time, but it is not so (at least in Sonoma). So AP tries to download a file that it needs and waits... if the files are many and large, you think it is stuck and you kill it. Maybe that all is working perfectly, then iCloud changes the situation under its feet, and, a little later, what before was going well is stuck now. I could prove it in almost two cases. You can inhibit this behaviour switching off the iCloud Drive optimisation, but in this way you loose the possibility to remove the download for the folders that you want to keep only on iCloud. I appreciated very much the new suggestive animated backgrounds... and also the new merry emoticons in the latest version of MacOS.... but from time to time they should also try to fix the old pitfalls of a service that you, in addition, pay each month for, and which always used to generate troubles since many years. All that to warn other unlucky users or to be warned if my conclusions were wrong.