Jump to content

nwhit

Members
  • Posts

    737
  • Joined

  • Last visited

Everything posted by nwhit

  1. Unless a moderator has other info, I don't think documents store user interface prefs such as the Background Grey Level, Font UI Size, UI Style, etc. No matter what I delete, no matter which version of the beta I reinstall after trashing the app, all those prefs are still there, which indicates I have not fully "uninstalled" the app. And trying to resolve my issue with copy/paste text blocks from InDesign really needs to see if deleting the app (completely) and reinstalling will solve that serious problem. I wish someone from Affinity could comment on this.
  2. Nowadays most all prefs are in the user Library (~/Library). Anything with Pub or Publisher was deleted. I also did a search in the main/System level Library but didn't find anything there. After doing the Ctrl Open routine and selecting everything, that didn't clear all prefs - just the things it listed. There were still other prefs that had been set at the original install, so that method doesn't "uninstall" the app. Apparently Serif is storing APub prefs somewhere else in addition to the Library items with affinitypublisher in the name.
  3. What your saying is that we never have been able to copy text blocks from InDesign and paste them into APub without them becoming single lines of text? I could swear we had done that and had posted that the ability to do so made it possible to use APub with our existing ID files and client work. I'll admit that we've been doing a lot of other things while testing APub but I sure seem to remember copying/pasting successfully.
  4. This is the same file as the screen shot done before back when copy/paste worked. Other than it tied together the headline text block with the first column of text, most of the multi-page document came in pretty good as did several other ID files. But now none of them will copy/paste.
  5. As per the request of the Moderator in Suggestions/InDesign thread: "I am not aware that this code has been changed. If you are sure this is true of the same ID file coming into #58 and #128 please can you make a new thread in the Affinity Publisher bugs forum and attach a file that shows this regression (tell us which part you copied and what version of ID you are using to do the copy). Thanks" Using the first beta, I was able to copy/paste entire pages from multiple ID files (CS5 v7.0.4) into APub pretty successfully and most all text blocks came in correctly. I also had success Placing PDF's of those same ID docs with preserved text blocks. However, after upgrading to the second beta, any and all copy/paste from the same ID files now brings in a new text frame for every line of text. The ID text block now comes in as a group of individual text frames for each line of text. I've deleted APub prefs, deleted the app, restarted the computer, reinstalled the first beta, etc. Cannot resolve why this has changed and is no longer working. macOS Sierra on an iMac. InDesign file attached and screenshot of a copy/pasted ID doc. Northumbrian_Aero_Start_-_Print.indd
  6. I also just deleted all affinitypublisher prefs found in the Library folder, deleted the app, reinstalled the first beta. It still has the prefs I set for the working area background color, interface size, etc., which indicates it is not starting APub from scratch.
  7. I also looked at this posting on Resetting Prefs, but none of this resets all the prefs.
  8. In Sierra??? Control/Ctrl is a contextual menu and can't be used with Open.
  9. No, looked at that but it only resets certain limited initial settings and not all prefs.
  10. Sadly, the ability to copy/paste from ID files apparently no longer works after the last beta (58) and newest (128) updates. Now get all text as singles lines of text and not the ID text blocks. Same happens when using Place with a PDF. Can't even select a single ID text block and copy/paste. End up with multiple lines of text as a "group" but not functioning as a text frame (block). Opening a PDF does keep most text blocks intact, although it also ties multiple blocks together that don't belong together. I hope they get this fixed since we can't really proceed with much testing since everything we do is related to past ID docs needing updating or serving as a template, etc. Running Sierra on iMac.
  11. With the serious problems I'm having in not being able to copy/paste text from ID, I have tried to delete all prefs and reload the beta app 128. But apparently looking for affinitypublisher files in the ~/Library doesn't remove everything. I've done that twice, but when I then open the beta, all my previously opened files reopen and most all of my previously set prefs are there (background color, interface font size, etc.). What do I need to do to completely uninstall the app and prefs? I really want to get file transfers from ID back again like I had in the first beta so that we can continue to test the app. Thanks.
  12. Opened doc made in previous beta by copy/paste from ID file. In the newest beta, opened doc, opened Resource Manager, selected all images, clicked Link button. It then opened a dialog asking what folder are the linked files in. When I canceled (since the images were in a number of different folders), app crashed.
  13. Just downloaded the newest beta (128) and the copy/past and importing a pdf into APub is still broken for me. Copy/pasting or Placing a pdf still brings in text as single lines of text instead of the text blocks from the ID file. I know it worked fine in the first beta, so not sure what is wrong. Are others having this issue or is it a local problem? The first beta had me thinking we could go ahead and start using APub using the copy-paste from old ID files, but with that not working, can't really use it at all right now. I even trashed the previous beta prefs, etc., but still have the problem. Anyone else have it working on a Mac where copy/paste brings in the correct text blocks?
  14. Just tried it with another ID document and have the same results. All ID text blocks are coming in as individual lines of text. I'm suspecting that this is different from the first beta because I had copied/pasted from an ID file and it all came in pretty well perfect with text blocks, etc. Hopefully will be fixed in the next release. I had been encouraged that we could bring in legacy ID files, but now it won't really work with multi-page docs and a lot of text blocks.
  15. Just had this same thing happen. I had reported previously that I was able to copy and paste an entire page from ID into APub and it came over almost perfectly. That was very encouraging. But today I was trying a different A4 doc that we routinely modify and send out as a pdf. In this case, I opened the ID file, copied everything, then pasted that into the newly created APub doc (v58). Unfortunately, this time every line of text came over as a separate text frame. And I doubt there is an easy way to join them back together. I then tried to copy just a full text box from ID and paste into the APub doc, but it again converted it into a text frame for each line of text. I then created a new blank text frame in the APub doc, copied the text itself in ID, then pasted that into the APub text frame, which worked. Not sure why it did not work correctly this time. I can't remember if when I did it with a fairly complex ID file and it worked fine if it was possibly with the first beta. Thus don't know at this point if it is an issue with this particular ID file or with APub 58. Discouraging since it had worked so well before in the previous testing. PS - Does the same thing when importing an ID-generated pdf of that ID doc.
  16. Hadn’t even looked at that, but you’re right. Mine is the same for hyphenation.
  17. I'm running Sierra, but Affinity apps seem to be picking up other language libraries from somewhere. Even in TextEdit and Mail I have the choice of US or UK English, so this seems peculiar to Affinity.
  18. That's been a standard with ID for years and it is how you move or send a working/unfinished copy of an ID file to someone. But it is still based on linked files. It simply collects and puts all the linked items, including fonts if desired, into a companion folder for delivery. If someone doesn't fully understand or appreciate why linked files are the "normal" method for placing graphics in DTP, it goes back to what I used to try to get across to my students at university. Without broad-based experience, you might simply not know what you don't know! Based on a very broad spectrum of media producers in both print and video (in the beginning, in the middle and even today), linked was and still is the "norm" and embedding is the option when needed for a special reason. But you are right that it should simply be a main pref that can be set and sustain for all new docs in order to fit a person's pref.
  19. All Affinity apps have had an issue with sticky settings and still do. Very difficult to use many things since very little of a person's settings and prefs stay, and that really needs to be worked on in all the apps. That said, linked files have been the mainstream setting since Pagemaker when it all started and, as stated, is a fundamental for an app like this. If an individual wants to use embedded, it is there to be used. And, yes, it should stay sticky as a pref. But it should not be the default.
  20. Still have the issue where I cannot see the two languages I have set in macOS prefs (US English and UK English). Instead all I get in the Character/Language drop-down is a single English and a bunch of other languages that are never used on this computer. In ID I can select their UK and US English dictionaries, but for some reason in Affinity apps I get a bunch of extraneous languages but not what I have in my system prefs. Someone in the first beta reported that on their iMac it was working correctly, so not sure why it does not work on mine.
  21. You might have the issue of APub occasionally loading APhoto menus. Try quitting and restarting the app. See the thread on the Photos menu issue.
×
×
  • 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.