Jump to content


  • Content count

  • Joined

  • Last visited

About Rabari

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Helsinki, Finland

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Rabari

    Memory leak?

    Open, no full screen, no documents open
  2. After using 1.7.0. extensively I left the app open overnight and through the next day (with no documents open). When i returned tonight Photo was unresponsive. I checked Activity Monitor and it showed Photo consuming over 70 GB memory. Note that Publisher was also running at the same time – any connection? Similiar things happened during the Beta, but at that time the app also consumed all virtual memory, and subsequently all free space on my startup SSD. This didn't seem to happen this time with 1.7.0. The disk looked normal, although the Photo memory use reported by Activity Monitor looks extreme. Mac OS 10.14.5 Mac mini Intel Core i7, 3 GHz, 16 GB
  3. Workaround for problem 1: Deselect "Separated mode" in Window menu Reselect "Separated mode" in Window menu Document shows in main monitor.
  4. Setting via Hyphenation option. It's great that Publisher finds it, after I manually, and every time the app is updated, install the hyphenation file in the Application bundle. The problem is not that I can't get hyphenation working. My point is that mucking about in the Application Bundle has never been a recommended activity, and certainly nothing you would instruct inexperienced users to do every time the app is updated. So the shipping version should recognize other places. The user/Library/Spelling folder would be better, even if it resides in the (nowadays) hidden Mac Library folder.
  5. I was asking, as creating a Spelling folder inside my user folder did not work. As did not, eventually, using the Spelling folder in the /user/Library folder. I can get hyphenation working only by installing the hyphenation dictionary directly into the app bundle. Tedious.
  6. I'm using the Mac version. Did you mean /Users/user/Library/Spelling/ I tried this. Did not work, other than Swedish showing up as a language choice for text. Hyphenation only works if the sv-SE folder is inside the application bundle. Contents/Resources/Dictionaries
  7. I made a Swedish hyphenation dictionary from the Open source files at Libre Office, but it's getting tedious to install them in the actual application package every time the beta expires and there's a new version available. Couldn't the language dictionaries be stored somewhere outside the app package? For instance in a /Documents/Affinity/Dictionaries/ folder. I attach the Swedish hyphenation dictionary folder for anyone who wants to use it when trying out Publisher. sv-SE.zip
  8. In my case opening old ID files in Publisher would be somewhat useful only for some select serial publications that i layout, and only to save some time during the initial switch. Back in the day, when i started using ID, it seemed important that it could open old PageMaker files, but the conversion most often required so much cleaning up, that starting from scratch would have been just as easy (or cumbersome, depending). Now I've found that copying text from existing ID projects and pasting it into Publisher brings the styles along. This is more often than not quite sufficient for me, as the design principles of the two programs are somewhat different, and things nevertheless have to be updated and adjusted. I understand that for very complicated files IDML import could be a benefit, but then again, the conversion would probably not be a hundred per cent accurate, so a lot of work would still be necessary. So for me, the lack of IDML import is not a dealbreaker for a first version of Publisher. Transitions are always a bit messy, but keeping two programs around is in my opinion not a problem. I even have an old system 9 installation with PageMaker on an old G4 Mac. I have never, ever actually opened PageMaker since I switched to ID, but hey - just in case… More important will be the ability to open 32-bit ID CS6 in the rare cases it will be necessary in the future. So as MacOs progresses, I'll probably keep the Mojave installation with ID around on a separate disk.
  9. The app looks very promising! However: I use a 2 monitor setup, always. I arrange all the separated palettes on my left monitor, which leaves a nice, clean working space on my main (menu bar) monitor. Problem 1: When I open a document, it opens on the left monitor, BEHIND all the palettes, not on the main (menu bar) monitor. (If I remember correctly, this occurs in other Affinity applications as well) Problem 2: After a hard crash, the windows more often than not revert to the standard one monitor setup, and I have to painstakingly rearrange my palettes to my preferred layout. A palette/window setup manager is needed.
  10. I use a two-monitor setup, and it would be essential for Publisher (and for the other Affinity products too) to have the ability to save my palette layout. At the moment, after an update (or a crash), everything resets, and I have to painstakingly recreate my setup.
  11. The ability to Automatically convert tabbed text to tables would be a real time-saver. (This would also go a long way, before Publisher has a robust word processing file importer. Right now, copying an pasting a table from Word to Publisher results in tabbed text) .
  12. docx is the important format. Crucial for the importer to recognize: any soft formatting (so I can change italic and bold to proper character styles) footnotes and endnotes indexes tables