Jump to content

ETC

Members
  • Content Count

    11
  • Joined

  • Last visited

About ETC

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @BeauRX One very good option for producing e-books is Vellum (www.vellum.pub), but only if you use a Mac. However, you have to use Microsoft Word to prepare the material for it. It is worth looking to.
  2. Thank you, Jon P, for your explanations and for improvements in 1.8.2. I'm no Affinity Publisher power user, and at this point the only thing I'm trying to do with it is make a calendar, which I just come back to periodically to work on. I just updated to 1.8.2 and when I applied Master A to a page of the calendar; a note did come up about something being detached, but it disappeared before I got it read through. Now I've used Undo and gone back, and here it is (image below). Interesting that although it has an "X" to close it and a "Close" button, it disappears all by itself. Seems to me that Affinity Publisher should let you chose which elements you want to re-apply from the Master Page. At is it is not it's all or nothing (best I can tell). To me the "Clear" or "Migrate" options under "Replace Existing" are anything but clear. I think where it says "Content:" it perhaps should say "Non-Master Content:" or something like that; also, the logic of "Migrate" escapes me: Master Page content is migrating to the Regular Page with both options (with "Clear" and with "Migrate"), but with "Clear" Master Page content is replacing the Regular Page content, but with "Migrate" it is being placed over (being appended to) the Regular Page content. Just seems very unclear to me. I hope my observations are constructive. You've (plural) made one nice piece of software! Thank you for your time and help on this.
  3. Hi, Walt, Thank you for that info. I posted it here: https://forum.affinity.serif.com/index.php?/topic/109915-master-pages-to-pages-forcibly-unlinked-attributes-no-way-to-re-link-them/
  4. Hi, Affinity Developers, I think this is a bug that perhaps hasn't been reported in this forum. Please see for the original post and some responses. I suppose this is by design, but I hope not. The problems I see are … (1) elements on a regular page that come from a master page are unlinked by Affinity without the user actually knowing it's happening. By comparison, in InDesign one must use Cmd-Shift (Mac) or Ctrl-Shift (Win) to override items from a master page. I think it's important that there be some way of forcing the user to make a choice so he or she knows what's going on. Just doing it behind the scenes without even notice seems pretty bad to me. Reason: one later changes the master and assumes the changes went to the regular pages, but they didn't. (2) Even worse, in my opinion, is that once the master page are unlinked on regular pages, there is no way to re-link them (best I can tell). One can see that they are unlinked because of the orange dotted vertical lines in the layers panel next to affected elements. But it seems that links of elements to the master page cannot be restored at all. Here's my example:
  5. Yes, but I don't understand why. If you add text to a table on a normal page both the Text & Text Frame attributes are unlinked. I would have expected only the Text attribute to be unlinked. Which would mean you could freely change the fills and borders on the table on the master page and have these updated on normal pages. Hopefully, this is a bug which can get sorted in the future. In comparison, if you add text to a text frame (from a master page) only the Text attribute is unlinked. The Text Frame attribute is not affected by the adding of the text. You need to do other stuff, than simply adding text, to get the Text Frame attribute to unlink also. I'm trying to use Affinity Publisher v. 1.8.1. Does anyone know if this problem in on the radar for fixing? I'm working on a calendar and had a table on the master page (the table is just the dates, which, of course, have to be in different boxes for each month). Text, Text Frame and Baseline grid are all unlinked attributes, so all the tweaking I've been doing to the master page table to get it right has been wasted, since it won't update the regular pages. Ugh! Is this issue mentioned in the bugs section of the forums? I would hope that never, ever would something become unlinked without the user specifically authorizing it, but that it gets unlinked and then there is no way to re-link it is even harder to accept.
  6. Callum, I appreciate your showing how to do that. I see many uses for this automatic renumbering of text. Thanks for your video. Eric
  7. To the best of my understanding, I understood and understand both settings. They aren't working as expected - i.e., on my machine with this file they are not working as you describe. That's why I would like to privately send a file to the devs. If there were an easy way to insert Lorem Ipsum in the entire document with various width letters randomly replacing letters of similar width (so the general "size" of the text remained similar), I'd do that and upload a sample file. (Nisus Writer Pro for Mac has a nice macro to anonymize text that way for submitting to support; love it!). I'll await the devs. Or the next beta.
  8. @A_B_C, Thank you for your help. I wasn't sure where I was supposed to post the bug report. I understand now. I have re-posted it in a New Topic over there. ETC
  9. Possible bug: As it is now in the Release Version (1.7.3) and the Beta (1.8.0.502) if you have Paragraph > Flow Options > "Justify Vertically" turned on and the text flows from text frame 1 to text frame 2 and you would have an orphan without "Prevent widowed last lines", the text at the bottom of the first text frame does not go to the bottom as it should to be "justified vertically." If you shut off "Prevent widowed last lines", the text is justified vertically as it should be, but now you've got a widowed last line at the top of the next text frame. I don't want to put the file up publicly, but I'd be happy to share it with developers. Is there an address to which I could send a link so the developers only can download the file and check it? Or maybe they can just duplicate the problem themselves without my file.
  10. I found what I think is a bug in Affinity Publisher beta 1.8.0.502. This is from my first post to this forum: Probably that wasn't the right place to post. Sorry. Possible bug: As it is now in the Release Version (1.7.3) and the Beta (1.8.0.502) if you have Paragraph > Flow > "Justify Vertically" turned on and the text flows from text frame 1 to text frame 2 and you would have an orphan without "Prevent widowed last lines", the text at the bottom of the first text frame does not go to the bottom as it should to be "justified vertically." If you shut off "Prevent widowed last lines", the text is justified vertically as it should be, but now you've got a widowed last line at the top of the next text frame. I don't want to put the file up publicly, but I'd be happy to share it with developers. Is there an address to which I could send a link so the developers only can download the file and check it? Or maybe they can just duplicate the problem themselves without my file.
  11. Because it deals with widow-orphan issues, I thought the fixing of the bug mentioned below (which according to a post above is fixed in Beta 1.8.0.499) would have fixed the issue I found, but it did not. I just downloaded the Beta 1.8.0.502 and launched it. The file I had problems with still has problems. My problem: As it is now in the Release Version (1.7.3) and the Beta (1.8.0.502) if you have Paragraph > Flow > "Justify Vertically" turned on and the text flows from text frame 1 to text frame 2 and you would have an orphan without "Prevent widowed last lines", the text at the bottom of the first text frame does not go to the bottom as it should to be "justified vertically." If you shut off "Prevent widowed last lines", the text is justified vertically as it should be, but now you've got a widowed last line at the top of the next text frame. I don't want to put the file up publicly, but I'd be happy to share it with developers. Is there an address to which I could send a link so the developers only can download the file and check it? Or maybe they can just duplicate the problem themselves without my file.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.