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

AlanPickup

Members
  • Posts

    406
  • Joined

  • Last visited

Everything posted by AlanPickup

  1. Hi Jon P Thanks for this information which I enabled pdf logging and this has enabled me to tract down the faulty url which was an email address where it began with a capital letter. When I changed this to lower case and eidted the hyperlink the export worked. When exported with the capital letter in 1.9 the hyperlink still worked with a capital letter and opened an email form. Hope this helps
  2. Moving details over to this thread as requested in previous reply from Gabe First post in the other thread Hi I have reported this previously so this is just an update to say it is still present in latest windows beta. If a document has an erroneous hyperlink in the interactive section the size of the published pdf document will not be calculated and the export will return an error. If saved the file will still open in the current retail version, but needs to be sorted before the beta goes to release as will not have hte option of using the release version to get over the problem. Just coompleted a 20 page newsletter in beta, during which I have had two updates to beta, as there are a lot of hyperlinks in the document it is hard work trying to track down. This has only happened over the last couple of days as it exported previously from beta, but may be content I have added or amended. Another interesting point is if my internet connection was down would this give the same error, just speculating as I have tried to check all hyperlinks from the published pdf from retail and they seemed to work, but I got a dropped connection whilst testing one, but it worked when the connection came back to the internet. I am not going to post further as it must be hyperlink related and if it appears in another project without hyperlinks then I will followup. Fortunately it is not causing a problem as the file will open in the retail version and export. I can only presume the beta is recognisning something as an hyperlink that I have not formatted as an hyperlink
  3. No it is another file, I exported in release version and reckon to have checked all hyperlinks in the pdf, but as I have been adding pages most of last week it is hard to pin down when it started happening, At the start of the week i was exporting in beta no problem, but there have been two updates since I started and I have added more content. There are a number of passthrough pdf leaflets added to pages, they are in 1.5 or 1.3 so I have exported in 1.5 pdf so that thet will not be rasterised and increase the file size. There are a number of embeded hyperlinks that may relate to icons for social media, but againI think I have checked them all?
  4. I have tried all the hyperlinks and they all work and export works in 1.9 retail, but will not calculate export size in latest beta, which worked up to two latest updates and gives error occured if I click to export. If you need a copy file please provide link to upload
  5. Hi I have reported this previously so this is just an update to say it is still present in latest windows beta. If a document has an erroneous hyperlink in the interactive section the size of the published document will not be calculated and the export will return an error. If saved the file will still open in the current retail version, but needs to be sorted before the beta goes to release as will not have hte option of using the release version to get over the problem. Just coompleted a 20 page newsletter in beta, during which I have had two updates to beta, as there are a lot of hyperlinks in the document it is hard work trying to track down. This has only happened over the last couple of days as it exported previously from beta, but may be content I have added or amended. Another interesting point is if my internet connection was down would this give the same error, just speculating as I have tried to check all hyperlinks from the published pdf from retail and they seemed to work, but I got a dropped connection whilst testing one, but it worked when the connection came back to the internet
  6. If you mean upload to have the T shirt printed the printing compay will automatically know the image is there in their software, my even show up in the upload process. I had some lanyards created with a white design on a blue background and just sent the png file. I also had some t shirts printed and the software on thier website allowed me to see the result on different coloured shirts after the png was uploaded.
  7. If you use the built in windows image viewer you can alter the settings to use Dark mode, you will then see the white image
  8. Not sure if this is across the board fro everyone but the thumbnail icons have suddenly started showing an image on the thumbnail, even on previously created files?
  9. Hi Jon Unfortunately it was the first saving of the file in the beta so I have no previously saved versions. I have opened the version created with retail APub with the beta and expereinced no problems saving it. My preference is to embed images and when creating the original beta I got the message about linking to save space which I accepted, when copied and pasted to the retail the linked remained. Just as an aside for the first time I got a thumbnail image when saving directly to my One Drive linked folder, previously they have only saved the app logo. Checked this was also the case with apub and Afdesign files created previously, which is good news hope it stays
  10. I have received the following error when trying to save a file in beta, the file save as zero bytes and is read only and will not open If there is any other file in the app data folder you need let me know. I created the same blank publication in retail and copy pasted the contents of each page over and is saved no problem. Only difference is I had some of the layers locked in the beta but had to unlock to copy and paste.
  11. Thanks Jon I can confirm I have altered the twitter link and it exported the pdf and calculated the size OK using the beta. It would be good to have this check feature pop up in the preflight warning with the option to ignore and publish. Also that faulty hyperlink was in the document in the original "bug" report so that is solved also.
  12. Uploaded the file, this has just happened again with another flyer where we have updated the template and I have copied and pasted the content on to the new template, again that one worked fine in the release version. I have also tried moving the file to a non one drive location (installed hard drive) still same error but the hard drive location instead of the onedrive
  13. Hi I have again come across this problem in the latest Beta .1085 this time with a single page flyer that was done on a document created from a flyer. In Beta message Same file opened in release version and no export problems. Need to bottom before the beta is transferred in to the next realease version, post link for file if you want a copy please
  14. I have used PagePlus to design editable pdf forms and out of interest i tried placing one of these in an APub document, and I think what Joachim means is that although the pdf fields showin in Apub they do not carry through to the pdf when exported see below Apub screen grab and pdf export screen grab. The blue hilight elements are fields I have used pdfsam basic to merge a aPub pdf with an editable pdf from another app
  15. Though it is not obvious if you look at file explorer One Drive does synchronise your desktop, hence Affinity files will not show the thumbnails. However if you save the file to a folder created outside of onedrive i.e. created directly on your C drive or other internal driv not connected to onedrive the thumbnali will appear when using icons in the view type. Example below of a folder I created on desktop to send a test file to Affininty. I opened the file saved the file to my internal H drive then moved it back to the desktop folder by dragging
  16. Having the gradient tool selected get you the control of direction when you hav eselected gradient from the swatch pallette
  17. They would have started out square or rectangular when printed and then cut & creased in post production at the printers.
  18. Hi my C drive is an 1TB Intel 660P M.2 PCIe 3XS which has my operating systems and one drives (business and personal) My D drive is an installed Seagate 2TB Barra ST2000DM008 which I use for my collections of music and my DAM as Affinity thumbnails will not show in one drive, but my working files are on the the C:drive in One drives. My desktop is on my C drive and synchronises with my laptop. I have just started up my laptop which has a C drive 500gb ssd and a D drive 1TB harddrive, my onedrive on this machine is on the D drive and I have exactly the same problem it will not export the pdf to any drive with the beta version Just an aside I was puting a colon after the drive letters and you get this 😄 on the forum
  19. Everything is on the One Drive for both the A4 and A5 versions inc all assets. They export is fine with the release version to pdf, but not with the beta. I tried the beta saving direct to the hard drive (as an aside I have to save or move Affinity files to this drive to get thumbnails) the results were just the same gave up after 3mins waiting for it to calculate the export size and exported without success see below. Opened up again in the release version calculated file size in about 5 seconds and exported to the hard drive without any problems
  20. Definately slow in loading on very high broadband. others sites almost instant. Forum take a few seconds
  21. To undock the window you just drag on the top tile bar of window, you can then see both windows. However another problem arises when you try to drag and drop in that the layer order is not maintained, which is a bit of a problem may be needs someone who uses the method to have an idea of maintaining layer order
  22. Hi I have a 16page A4 Document that produced a pdf at 96dpi at the standard Affinity setting (i.e. used the small pdf and increased the dpi.) this gave a pdf around 8mb. the affinity file size was about 40mb. To see if I could get a smaller pdf I resized the affinity document to A5 using all spreads, the results where good and the resultant pdf dropped to 5mb, however the affinity file size doubled to 80mb. Thought I would try the A5 version in this new beta. First it would not calculate the pdf size for export, after 3mins without the size being generated I tried export. First attempt it did not give the warning that it was going to overwrite the existing pdf file and the operation failed saying error occured and the location on my one drive. I closed the file and opened in the non beta and it work fine. I then opened again in the beta it still did not calculate the export pdf size, but when I proceeded it gave the overwrite warning but the operation failed again the beta error log is as follows [DXCore] Found 2 adapters NVIDIA GeForce GTX 1660 SUPER Version: 27.21.14.6259 IsHardware: Yes Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_10DE&DEV_21C4&SUBSYS_10680000&REV_A1 LUID: 0xCDC6 Microsoft Basic Render Driver Version: 10.0.19041.546 IsHardware: No Supports D3D12 Feature Level 12.0: Yes HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0xE095 [DXGI] Enumerating adapters NVIDIA GeForce GTX 1660 SUPER HardwareID: PCI\VEN_10DE&DEV_21C4&SUBSYS_106838420000&REV_A1 LUID: 0xCDC6 Microsoft Basic Render Driver HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00 LUID: 0xE095 [OpenCL] Found 1 platforms: Name: NVIDIA CUDA Vendor: NVIDIA Corporation Version: OpenCL 1.2 CUDA 11.2.162 [OpenCL] Found 1 devices for platform NVIDIA CUDA: GeForce GTX 1660 SUPER Vendor: NVIDIA Corporation Version: OpenCL 1.2 CUDA If you want copies of the Affinity files please provide a link
  23. Whilst I have not experienced this with Affinity I have had problems with Winodws 7 updated to Windows 10 with a few programs wanting me to re-install each time I used them. I have now installed clean copies of windows 10 on all my machines and do not have that problem any longer. Think it was something to do wiht redundant 32bit items left over in the upgrade.
×
×
  • 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.