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

Dom159

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by Dom159

  1. Same thing happening to me, but in Publisher. Using a laptop, internal hard drive. There's no reason why it should have lost access to any of the files.
  2. Did anything ever come of this? I am still getting this behaviour, but only with one style. The styles are identical.
  3. I am experiencing the same problem. Everything was fine until a little under a week ago. Each year I produce a wall calendar. This is the third year I am using Affinity Publisher for the job. I had begun the layout for next year, and realised that all my text styles were missing. So I imported them from last year's Publisher file. Everything was fine until I scrolled down the list of text styles. Then Publisher just freezes. It begins to scroll, then becomes jerky, then freezes. The memory use of Publisher just continues to climb, and there is not option but to use the task manager to kill the program. So I decided to select "Show Hierarchical" from the context menu of the Text Styles panel. This caused Publisher to immediately freeze. How it freezes as soon as the file is opened. If I open a new document it's fine. If I import the styles from last years calendar into it, as soon as I scroll through the styles it freezes. I opened last years calendar file, and it also froze once I scrolled through the styles. I have uninstalled and reinstalled Publisher. I am at a loss as to what to do. I really need to work on this project, but in is impossible right now. I've attached the crash report folder for Affinity Publisher in case it's of any use, and would really appreciate any help. SYSTEM INFORMATION OS Name Microsoft Windows 10 Home Version 10.0.19042 Build 19042 System Manufacturer HP System Model HP Laptop 15-db1xxx System Type x64-based PC System SKU 3R654PA#ABG Processor AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx, 2100 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date Insyde F.15, 06/11/2019 SMBIOS Version 3.1 Embedded Controller Version 51.17 BIOS Mode Legacy BaseBoard Manufacturer HP BaseBoard Product 85EA BaseBoard Version 51.17 Platform Role Mobile Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Hardware Abstraction Layer Version = "10.0.19041.964" Installed Physical Memory (RAM) 8.00 GB Total Physical Memory 5.95 GB Total Virtual Memory 14.4 GB Available Virtual Memory 2.33 GB Page File Space 8.50 GB CrashReports.zip
  4. Brilliantly articulated — well done that man! The floating panel idea is great...please Affinity, get this feature sorted out. I should also mention that while I'm using Publisher, not Designer, then align tool functionality is the same.
  5. Just want to add my voice to this thread to say that I too would love to see the align function returned to the way it used to be. This change to the align dialogue seems completely unnecessary and is very annoying. Everyone's been used to it being the other way around, and now it's changed apparently for no real reason....if it ain't broke, don't fix it!
  6. Yes please! This would be a really useful feature.
  7. I would not mind, but it seems now that it would not be helpful, as the problem is no longer happening. As I said, when I recreated the export preset, the problem ceased, and it functioned correctly. I deleted the defective preset as soon as I discovered that it was the problem. So I can no longer recreate the scenario in which the gradient failed to render. Thanks though for your willingness to help. I can only imagine that the previous export preset I was using must have been corrupted somehow.
  8. I use XnView MP as an image library/browser, and I drag a lot of images from that program into my layouts in Publisher. I have a lot of layers, and the newly dragged item always goes to the top of the pile. Is there a way to place the dropped item above/below the currently selected layer?
  9. Thomaso, thank you for your explanation, which was helpful. I was using PDF version 1.7, so that should not have been a problem.
  10. Thanks for the reply. I understand that. I was just surprised that a gradient fill would be an "unsupported element". When I exported with "rasterize nothing", the gradient was lost. Only by rasterizing could I get the gradient to remain. I think the problem is solved now anyhow. There must have been some corruption in the export preset I created, because when I created a second preset with identical settings, the gradient exported correctly without the need to rasterize anything.
  11. Okay, there was something wrong with the pdf export preset that I created. When I recreated it using exactly the same settings, it exported fine, but when I went back and used the original preset, the same problem with the gradient occurred. I can't see any different between the settings on the two presets, but something must be wrong with the first one. Anyway, it seems to be working fine now with the updated export preset.
  12. Hi, I have used Adobe Indesign for many years as an amateur, and am now making the switch to Publisher (I used the beta since its release). I have a project which makes a lot of use of empty boxes with a gradient fill, white to transparent with the starting opacity of the white at about 80%. When I export to pdf, the gradient is no longer there; the whole box is filled with solid white at 80% opacity. I can make it export correctly by changing the export settings to rasterise unsupported elements, but this causes other elements to be rasterised which I do not want be rasterised. Can gradients really be an unsupported element in Publisher? Thanks so much for your help.
×
×
  • 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.