Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

597 profile views
  1. That's what I did, too. But just having a simple "copy" indicator would be a big improvement.
  2. Yeah, master pages without descriptive names are useless to me in setting up full sized books having so many distinct parts. If I was doing a brochure, I could probably get away with two and not get confused. "They" (Big Desktop Publishing) should do something to mark duplicate copies as copies to help those of us working on bigger documents stay organized.
  3. In the layers panel, I'm used to clicking Command J and getting a duplicate layer above the one selected. That is the new one. When I duplicate a Master Page, I cannot tell which is the new one — the one on top or the bottom? It does not say "copy" or "(1)" or anything. So if I start applying things to that page — OR DELETING THEM — it could cause issues in my document using that Master Page if it's not clearly marked as the active / in use master, or the new one. Anyone else knowmsayin?
  4. I found a solution and it's holding. But still, formatting the text in the TOC should be as simple and intuitive as doing it anywhere else. That is the high water mark for the programmers: MAKE TEXT STYLING THE TOC EASY. (Not a game of chance where everything is in flux and therefore unreliable)
  5. The OP asked for someone from the company to comment, but no one has. I can't blame them. I think this text issue is a sticking point with many people who are wondering "How do I export a tab-delineated index page out of APub?" only to realize that it's not possible to do so. In fact, I've read advice from various sources on the internet for procedures that I can't engage because of this one limitation. Not being a coder, I don't know how difficult it is to add this feature to APub. But I think it would make a lot of us happier. However, you can copy and paste directly from APub into rtf format and work with it there. However, there are often "gremlins" from program to program when copy/pasting, so the work is never as clean as it ought to be. My kingdom (if I had one) for proper text export. :)
  6. I've also noticed that my book manuscript crashed at times which related (in my opinion) to my needing to update the index. Or it was index related. I think the markers and the whole system of organizing a document sometimes gets dizzy and just faints. And when it does — I hear a thud on my desktop and a low moan as Apub hits the ground. Once revived, it remembers nothing of the event and we go on as before.
  7. You're very welcome. Glad to help. And...the proof is in the pudding, as they say. I stand behind what I said because it really gave me the kind of precision I needed in creating the kind of book that I did. I have some tables and lists and things that needed to stay in place exactly where I'd left them (top of pages, etc.), so breaking the text flow between chapters was the ideal solution. It may also be the first book in history without hyphens at the end of each line. That novelty alone is worth the price, I would think. In case someone is curious, here's my book entitled: Clearing a Path to Joy (And finding contentment along the way) (I've heard from a reliable source that it's pretty good.) Good luck with your project, btw.
  8. The two issues seem to have been related: when the TOC had all these duplicates, the numbering input system did not work. I guess the question now is "How did all these TOCs get into my document when it only has one TOC?" (being that it's a typical book, and I don't recall doing anything bizarre, like copying and pasting my TOC 13 times).
  9. Has anyone experienced this? I usually use the forward and backward arrows for navigating to a page in my book manuscript but today I entered (or tried to enter) a number and immediately upon typing a single stroke, the program crashed. This happened 3 times in a row. Just restarted my computer, just in case. I'm on an old Mac Pro using Sierra using APub 1.10.1. Works fine otherwise, so it's a mystery to me why this would happen. I did use number inputting at other times (previous versions?) without any crashes. No idea why this would happen now - except that I'm sending my book to the printer today. Could be a "divine intervention" thing; gotta consider all the angles. UPDATE: I was checking the preflight and it was asking me to update the TOC. I checked it and found that there were duplicate entries of the TOC. Well, 14 of them exactly. Okay. Luckily I'm working with a duplicate copy of my master file cause this is getting scary. BUT... I deleted those extra TOCs and I tried entering a page number and now it doesn't crash. Problem solved? Or is my file dangling by a thread from a cliff with the intention to jump? Stay tuned for more after this word from our sponsor. (Feel free to post your own random sh*t in the spirit of this uncertain moment.)
  10. I had the sluggishness issue (I believe) when working on the book cover. I had embedded the graphics. I then linked them instead. That may have helped. I haven't worked on the cover in a couple of days. I'll have to check on it again to see if the sluggishness is still there. I can't do metal on this computer. Too old - the card.
  11. No, please. Don't get up. I've got this. Anyway, I solved the problem and found a possible bug. I had to delete the entire chapter (20) — text and master pages — and then add the chapter one paragraph at a time into new content pages that I added. Why? Good of you to ask. Here's why. I have index markers throughout that chapter and when I added a paragraph that I could see the index markers on, the file would not save after that — in most cases. So it seems that some but not all markers got corrupted. I can't imagine what I'd do if the whole index went kaput like that... Anyway, I solved all of this by pasting that paragraph into another program, which stripped away all that marker-based coding, then I pasted it back into the book file and applied my styles again. Voila. It worked. Then I had to reassign the index markers/flags. It was tedious as f... to do it this way, but at least I found out what was crashing 1.10 for this specific file. On other files 1.10 seemed fine, but somehow the index markers got corrupted or may have been mistakenly detached from their origin (at the end of the book) and this created the error (I assume) about "bad access." Anyway, I got my book file working again. However, 1.10 seems kinda sluggish to me, unlike when I was using 1.92. That's not what the advertising says. I'm getting beachballs here on my Mac Intel. So yeah, I think 1.10 needs some tweaking to get it up to snuff.
  12. Yup. My Mac Intel Affinity experience is not what I'm used to. 1.10 has some molasses built into it. Pls clean the inner workings and apply a good quality grease.
  13. Once you learn the program, you can get that 3hrs down to 10 minutes as well. However, I think 1.10 has some lagging issues. I've noticed that too. It wasn't this slow in 1.93 (or whatever the last one was). Other than that (temporary issue) I disagree. I think it's a great app for publishing books, especially when you compare the prices for both. I bought my copy when it came out for $50 or so USD — and I've saved myself a ton of money since on not having to pay Adobe subscription fees — or $3500 for CS6 production suites.
  14. The transform panel has an angle setting; there are a lot of controls in close proximity there. Just blame the transform panel. That way you won't have to take the heat.
  15. Of course it had to happen. Last night I finished editing the last chapter of my book and shortly thereafter, the file started to crash upon trying to save anything I tried to write afterward. I have incremental saves, so I'm not "screwed" — but this is inconvenient. My path to disaster likely began when I added a couple of master pages. I then noticed that my epilogue had disappeared completely. Not because I deleted it (at least not intentionally). Anyway, saving a single word correction is now impossible. I'm on a Mac production machine using Sierra and other previous APub files work fine. So I have a corruption. What I need is a suggestion wherein I might troubleshoot what's causing it. I'm going to cut and paste into an older file and continue. I can't even do a "save as" (have to duplicate using Mac finder duplicate function.) Any thoughts (and prayers)? Suggestions? Thanks. I have crash reports, they seem to always suggest "bad access" but the exception codes are different for all three. I don't know what any of that means, but should there not be a consistent cause rather than a roaming one? Here's an example of crash #3: (truncated) Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000500000007 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [0] VM Regions Near 0x500000007: MALLOC_LARGE_REUSABLE 00000001ca8b3000-00000001caf8b000 [ 7008K] rw-/rwx SM=PRV --> MALLOC_NANO 0000600000000000-0000600007e00000 [126.0M] rw-/rwx SM=PRV Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fffc65ef34a mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fffc65ee797 mach_msg + 55 2 com.apple.CoreFoundation 0x00007fffb08822e4 __CFRunLoopServiceMachPort + 212 3 com.apple.CoreFoundation 0x00007fffb0881761 __CFRunLoopRun + 1361 4 com.apple.CoreFoundation 0x00007fffb0880fb4 CFRunLoopRunSpecific + 420 5 com.apple.HIToolbox 0x00007fffafddfebc RunCurrentEventLoopInMode + 240 6 com.apple.HIToolbox 0x00007fffafddfcf1 ReceiveNextEventCommon + 432 7 com.apple.HIToolbox 0x00007fffafddfb26 _BlockUntilNextEventMatchingListInModeWithFilter + 71 ETC...
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.