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

TonyMi

Members
  • Posts

    9
  • Joined

  • Last visited

  1. Hi carl123, This fixed the problem, so it was operator error not a bug!!. I didn't import/copy the text from somewhere else, so must have set it myself somehow, but I don't know how. Thanks for the help, I can now get back to the flowchart. Best Regards, Tony.
  2. Hello, I'm developing a Support Flowchart for our team and have come across a situation that looks like a bug. First to answer your questions: I'm using the latest version of Publisher. The problem is repeatable and has stopped my work. I don't know if it happens for new documents. I'm using Windows 10. Basically I cannot do any work on this document because whatever I want to do will automatically activate a particular text box (see the video) so no more work can be conducted on this document. No unusual hardware, no system changes since the last document that I produced. This 'bug' has completely stopped me moving ahead with this piece of work because whatever I do just activates the text box, so I'd be grateful to know if it's a bug (and any workaround) or if I've done something wrong to create this situation. Best Regards, Tony Minchell. Feel free to email me at the provided email address or call on 07810447569. 20210129_104154.mp4 Support Flow Chart.afpub
  3. I'm trying to do exactly what is described in this article, get a row of dots between the TOC item and the page number, but I just cannot achieve this. I'm unable to get this 'Edit Text Style' dialog box to appear. I have Table of Contents selected under View > Studio, but cannot find the Table of Contents as shown above. In the help file below, line 3 doesn't appear to work for me, ie, the double clicking does do anything, so I cannot get to step 5, adding the row of dots. I'd much appreciate some step by step help with this, to get dots added between the TOC item and the number. Many thanks.
  4. I don't have 'Use mouse wheel to zoom' selected, so it shouldn't zoom, but I do have 'Use scrubby' zoom' selected, but I don't know what scrubby zoom is. I shall de-select scrubby zoom and see if this fixes the problem.
  5. I don't know if this is a bug or a 'feature'. When I turn the mouse wheel I move forward and backward through the pages in the publication. If I move the mouse wheel fast the pages seem to zoom out so that I have many pages displayed on the screen at the same time. Below I had the page at full screen width. I turned the mouse wheel rapidly to move through the pages, and now have many small pages displayed. My system is Windows 10 Affinity is 1.7.3.481
  6. Hi Mike, This is good information and tells me what is going on. What I need to do is a 'Find and Replace' on the two Unicode values. I need to replace U+0007 with U+0020. I don't know if this capability is in Affinity, be great if it was. I'll have to look into this over Christmas, no time to do it now. Hopefully this'll be in the help file. You are also correct in that our out sourced people use InDesign, which I do not have. Many thanks for the clarification.
  7. Hi Jon, Attached is the file that I'm trying to work with. I'm wondering if this is a Font issue. The font in the document needs to be substituted, see image below. I've tried to find out how to add a new fonts to Affinity, but not found that info yet. I've reloaded the document, but the problem persists. Thanks for looking into it. I look forward to any suggestions that you can come up with. T3DSO2000_Data Sheet_17-12-2018.pdf
  8. I've just loaded Publisher .206 and tried to work with PDF files. A few bugs seem to have crept in over the previous version. PDF files are much slower to import / load and save / create as an output compared to the previous version. There are many errors in the imported / loaded PDFs, the most common one being spaces being replaced with a clear square block. Also sometimes images have moved and text has overwritten other lines. It could be my source file but I can edit it fine in Adobe tools without these errors, see the attached file, which is a pdf import / export from Affinity .206 without modifying the PDF. Also, I tried to regress to .192 but found that this didn't work. Running .192 seemed to delete the . 206 exe without installing the previous version (.192). So I've re-installed .206. I'm no PC expert so it is possible that my PDF screwed things up. Many Thanks. Affinity Test2.pdf
  9. Hi, Justify all seems buggy. I've been testing Publisher on some text and noticed that the 'fully justify' seems to mess up the final text row, see attached. So the first rows are fine, the last row should have been ignored by the fully justify, but it hasn't been. This has basically screwed up the final text word. Also, the heading is fine because that was not highlighted to justify, bit it too would have screwed up if it had been highlighted for full justify. It's a great product that is improving with every release. The Videos are useful but could probably do with being a little more depth when you get the time.
×
×
  • 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.