Jump to content
You must now use your email address to sign in [click for more info] ×

johndmoulton

Members
  • Posts

    32
  • Joined

  • Last visited

Everything posted by johndmoulton

  1. Wow! Thanks for this. That's an awful lot to take in, let alone exercise! I'm on a tight schedule to complete another picture book right now, so will need to get back to this later if the issue persists. Meanwhile, I can say that the layout is very simple. All 35 pages were imported to Publisher as .afphoto linked files at the exact size required (including bleed) and that I have not had this issue with my previous three publications, all of the exact same size and nature. Just weird!
  2. The issue appears to have been resolved and somewhat irritatingly, I don't know how or why, it just doesn't happen now! To answer you question, I did switch off auto - it's still switch off - but the problem persisted a while after that. Maybe kicked in on a restart?
  3. I have discovered that if on export (to PDF) I leave the default, File Settings/All pages as is, Publisher2 crashes every time. However, if I select 'Pages' and enter 1-35 (that being all pages in this case) it exports just fine. Publisher2 (Latest) iMac M1 Chip Ventura 13.3.1
  4. Here's the latest: I have discovered that if on export (to PDF) I leave the default, File Settings/All pages as is, Publisher2 crashes every time. However, if I select 'Pages' and enter 1-35 (effectively all pages in this case) it exports just fine. Given this, it seems I have a bug to report. iMac M1 (Latest version of Ventura (13.3.1)Using both Affinity Publisher 2 & Beta
  5. Old Bruce: I have never used page numbers in Publisher, or had any cause to address their presence (or not) in any of my previous children's picture books. They all exported first time and were accepted by Amazon KDP without issue, so I do not see page numbers as the problem. As I write, I'm just happy that even though I had to 'baby-step' Publisher into to exporting the whole book (see above), at least it's now done (without addressing page numbers) - but that doesn't mean there is no issue here - all very weird to me.
  6. Thanks, Old Bruce. But I don't want page numbers included, so this is not this issue. MEANWHILE ... AND THIS IS REALLY WEIRD! ... I tried Export the file again this morning and yet again Publisher simply shut down at 'go'. So, I tried exporting just the first ten pages - fine. Then I tried exporting just the first twenty pages - fine. Then I tried exporting just the first thirty (of the 35) pages - fine. Then I tried exporting all 35 pages again - and it worked! GO FIGURE!
  7. Hi Seneca, I don't use page numbers and so this does not apply. Here are my settings: Hi Seneca. I don't use page numbers and so this does not apply. Attached is a screenshot of my settings - which I believe are the same as usual for me.
  8. I just completed a 34-page picture book in Publisher. It saves just fine as a Publisher file, but when I try to export it as a PDF The program (v2) simply closes down! I saved a copy of the file and opened it in v2Beta and here, on save as PDF a pop-up (screenshot attached) states 'Nothing to export. All the pages to export are in sections marked not for export. No files have been exported." This will be the fourth picture book I have created in Affinity Photo + Publisher and I have never had this problem before. Am I missing something? iMac M1 (Latest version of Ventura (13.3.1) Using both Affinity Publisher 2 & Beta (see above)
  9. RC-R: Thanks for that. Found Display and switched off Auto. Time will tell. Thanks again for the input. J.
  10. Pšenda: I thought so too, hence the question: Why is a file's original path 'overwritten' by the path of the latest file opened and suggests that in 'Save As...'? Seems the system's 'memory' is only capable of storing the latest file path in that circumstance. So yes, 'Save' and Ctr-S suggest the folder the file came from, but 'Save As...' does not, once you have opened a second file with a difference source folder. I may want to create several versions of the same image in the same folder, but if I have opened another file from another folder since opening (in this case)' File A' the system goes to the latest folder accessed. So, when I want to save the new version as (say) File A2, the system goes to the latest folder accessed, NOT the folder the original 'File A' was sourced from.
  11. LeeThorpe: Thanks for this. It comes and goes. I do think it's a RAM issue, but disappointed as I thought the new M1 chip and loads more RAM than I had previously would put an end to watching the rainbow wheel spinning - sometimes even when I just move my cursor from one place to another! I can't test the computer's RAM abilities in other suites because I don't have anything as complex or 'RAM-demanding' as Affinity. BTW: I don't see >Display. Is it now 'System/User Interface/UI Brightness' that you are referring to? Thank you for your help. Love Affinity and your support. John.
  12. "Save As ..." Where the file came from, please! Here's the issue: I'm working on file A from Folder A. While doing so I open file B from Folder B in another tab. I am now working on two files in unison - sometimes important for continuity of colour etc. But when I come to save Illustration A with 'Save As ...' the system automatically opens the last fold I took a file from - in this example It automatically offers Fold B for File A. I know the answer is use the folder drop-down, but sometimes I don't notice, particularly if folded A&B have similar names. Then later, when I want to retrieve File A, I often wonder where it's got to or cringe at the thought that I failed to save it! Can't a file have a background (unseen) tag indicating where it came from so that the system knows where best to suggest saving it? BTW: I know Cmd/S already does this, but does that not work if I want to keep the original File A and Save As File A2. Hope that makes sense. John.
  13. Since moving to Affinity2 I am noticing long, irritating lags when using various (any!) brushes. Is there a cure for this? I'm seeing lots of posts about lag, but nothing that gets to resolving the issue. iMac. M1 Chip. 16GB Memory on Ventura 13.2.1 Artwork 8.75" square. 300dpi. Around 20 Layers. Basic to complex brushes no matter the tool - all the same. It seems the longer I work the more the lag. I have tried closing all other programs and even restarting the computer.
  14. Hi Walt: That's true - but I don't know how to create shortcuts - yet! BUT HEY, I THINK I HAVE CAPTURED THE MOMENT IN 'HISTORY' BUT I STILL DON'T SEE IT! OK Here goes: The screenshot with the horizontal circle is the moment I spotted the group had flattened, so I hit Ctrl-Z and the layers re-appeared - so - as suggested, I opened up 'History' to view the 'recorded' moment - but frankly, in my ignorance, I don't see what's causing it - do you? So grateful for your input. John.
  15. By 'flattened', I mean the layers are gone without me taking any action I am aware of. Attached is a toad I'm working on where you can see the layers: A base colour, His chest, his patches, his bumps and his backpack. The kitten (also a WIP) was build the same way: Base colour, patches, hair etc - but now it's all one (flattened) image - no layers. In the case of the kitten, I may want to change the base coat colour a little or add a shading layer between the base and the fur - but now I can't. Hence the question. Other than 'Layer/Merge Selected' (which I'm definitely NOT doing) what unknown action could I be taking, unintended keyboard shortcut for example, that is causing this?
  16. Hi Cullum. Hate to say this, but I haven't buttoned down exactly when it occurs. I just find a need to break open a previously created group only to find it's now flat! Must also admit, I have never delved into 'History'. I really do need to look into that as I'm hoping that I can then select actions to delete. Problem is, this month I'm on a deadline and have very little time for tutorials other than short snippets. Sorry! BTW: Two more groups 'flattened' tonight! NOTE: Affinity Photo2. 2022 24" M1 Mac Desktop. Wacom Tablet.
  17. Thank you for your comments - very much appreciated. I really am enjoying this journey and for the first time in my life I am earning good money doing something I love doing - seem almost wrong somehow! If you're interested, you will find more of my illustrative work at https://jdm-art.com
  18. Hi All. I'll be 76y/o in a few weeks (April 2023), so no spring chicken! Art has always been a self-schooled, serious hobby for me, working with colour pencils, water colour, water colour airbrush and oils. I have been comfortable doing fairly basic photo manipulation in PhotoShop for years, but dumped them for Affinity when they went subscription - and don't miss them one bit! So ... I thought, Why not give digital art a go with this wonderful new suite! Eighteen months in and - from absolutely nowhere - I have illustrated three children's picture books for two different authors. All have been granted Mom's Choice Awards, Honouring Excellence on all three and I'm working on a fourth as I write. I love working digitally. I'm a huge fan of illustrations by Beatrix Potter and I like to think my work is in that vein with a modern twist. I have attached a few favourites here. All created entirely in Affinity Photo ... Enjoy!
  19. Hi All, Several times now, after grouping layers, I find that they have later become flattened! Is something I'm doing causing this. I am certainly not selecting them for 'Merge Selected' (etc). Thanking you in advance..
  20. walt.farrell: I guess that's my point when I think about it. I WANT Protect Alpha to be an option with the clone tool so that I can go hard up to the edge of an item on a layer without the cloning spilling over. Hope that makes sense.
  21. I would love for the 'Protect Alfa' facility to remain visible when working with other tools that are governed by it. Right now, if I'm using the Clone Tool and want to add/remove the Protect Alpha facility, I have to go back to the brush tool to add/remove it there causing a workflow hindrance.
  22. Please consider: 1)The ability to drag guidelines from the ruler without having to leave the current tool in use to use the Move Tool. Just hover over the ruler bar then drag and drop. 2) I'm working at the center of a large image and want to delete a guideline. It would be nice to be able to move that guideline over EITHER the vertical or horizontal ruler bar to delete it without having to move/shrink my image to drop the guideline into grey/black space'.
  23. GOT IT! It was indeed a tiny selection area still live on a vacant pixel layer. I was able to grab what seemed like 'nothing' on a wide sweep with my pen. Dragged what I could not still see to the centre until it highlighted the dead centre horizontal and vertical guides dropped it. Zoomed in REALLY close and there it was! Deleting the pixel layer had no effect because 'selections' are omnipresent of course. So once seen I selected it, selected, 'Select/Deselect' and bingo! As carl123 said, my Koalas are now free once more. Thanks Carl and others, for you input. Hope this stays up here for others like me who do not see 'the invisible' and now know how to find it to perhaps free up there 'frozen' layers too. Attached photo shows the selection are dead where I moved it to dead centre - which is on the trunk close to the baby koala. My bad! John.
×
×
  • Create New...

Important Information

Terms of Use | 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.