John:

I am 80% sure that it worked at one point when I was testing. Now, most likely the reason it worked is the same reason it stopped working: they had not yet added in the more advanced and complicated multiple languages features and got that all to work. And so it was more straightforward: drop in your plain text list of words renamed with a .dic extension, right here into this folder, and boom: we'll add that list to the standard dictionary. ADD being the key word. Somewhere along the line of adding in the complex multi-language support -- which seems very nice, and I'm not sure how often anyone would want to spellcheck 15 different languages in the same document, but hey, if you want to be that granular, why not! (other than it confuses almost everyone) -- the RUDIMENTARILY SIMPLE feature of adding a custom dictionary got lost in the shuffle. Whoopsies! But now let's bring it back, guys. Seriously.

Thank you very much! Can't? Oh-ho, never say can't!

I meant what I said. Totally useless. If one goes to "Help" trying to obtain "help" and it instead describes something completely different than what you are trying to get help with, causing the waste of hours, then that is called "useless." The word "Dictionary" is used, standard, for exactly what davies (and I, and countless other people) was trying to achieve. You add a "Custom Dictionary" in Microsoft Word, in WordPerfect, in PagePlus, in Everything known to both ancient and modern man! There should be some sort of disambiguation!

Where is the dictionary.propcols file located?

See I am not the only one. We want Custom Dictionaries! This is RUDIMENTARY! Every program ever has this feature. How can you not have this feature? Where is the dictionary.propcols file I have heard about?

The "Help" on this matter was completely useless, too (obviously). This one obscure thread I managed to find was the only thing helpful anywhere. Thank you, Dr. Walt and davies236! No thanks, Affinity. Please, please, for the sake of sanity, for the sake of humanity; FIX THIS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Wow. This is incomprehensibly stupid. How is it possible that any word-related program doing spell-checking would not have this RUDIMENTARY ability to batch-add words to ignore. WHAT IN THE WORLD? I just wasted hours trying to make this work. I thought I remembered it working, in fact, in the beta test. How in the world is this possible? IT'S A LIST OF WORDS, PEOPLE! LET US ADD A LIST OF WORDS!

Hmm, max is only 16. Lame. Feature request: Lame mode. I only need full resolution and stuff rarely, such as when it comes time to print out another revision to a PDF.

Yes, it's some kind of paging-type behavior. I am not up on the details of modern memory management, but I have monitored the activity in Activity Monitor and basically it works and works building up the denominator in "Committed" Memory, until it's 14.7 GB. Then the disk activity stops. So I guess if I had 8 + 15 = 23 gigs all would sail sweet? It's just a bit annoying, because the whole document including all linked images should fit into my physical RAM! Three times over! So it shows some sort of disgusting inefficiency, which I guess is inevitable given the balls of mud (Windows and Mac OS) the good folks at Affinity are building on. Oh well. Thank you very much, Carl, for the confirmation that my gut feeling was on the right track. More power it is. Here's the specs since you asked: OS Name Microsoft Windows 10 Pro Version 10.0.17134 Build 17134 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name LAPTOP System Manufacturer Hewlett-Packard System Model HP ProBook 6460b System Type x64-based PC Processor Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s) BIOS Version/Date Hewlett-Packard 68SCE Ver. F.60, 3/12/2015 SMBIOS Version 2.6 Embedded Controller Version 151.78 BIOS Mode Legacy BaseBoard Manufacturer Hewlett-Packard BaseBoard Model Not Available BaseBoard Name Base Board Platform Role Mobile Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Hardware Abstraction Layer Version = "10.0.17134.471" User Name LAPTOP\john Installed Physical Memory (RAM) 8.00 GB Total Physical Memory 7.94 GB Available Physical Memory 1.96 GB Total Virtual Memory 14.7 GB Available Virtual Memory 8.26 GB Page File Space 6.75 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware No Hyper-V - Data Execution Protection Yes I'll see how much RAM this thing can hold...

OK, I got 1.8.0.584 loaded (this is on a Windows 10 laptop, should have mentioned that) and opened the document up. Initially it seemed snappy! Meaning: it was responding, not immediately going into (Not Responding) mode. I scrolled a bit. Then scrolled up a few hundred pages to a random different part of the document. Whoop, it didn't like that. Page doesn't load and it locks up. Wait a few minutes unresponsive. Finally starts responding again, in jerks and starts, as typical. Eventually able to scroll back down to the original part of the document (near the end). Here, pages load, images display, but it's pretty slow. Activity Monitor shows that Publisher is monopolizing the hard drive, as is its wont. Disk activity at 100%, and other programs have a very hard time getting any writes in edgewise; whole computer virtually unusable. Again, this has been my typical experience for some weeks or months now. So 1.8.0 is no worse, but also no better. Closed and reopened with image links broken (so that I don't have to feel like committing hari kiri). Looked around for any new performance-related options. Found none. So, any other ideas? Is there a hidden advanced Config file where I could tweak promising settings? Do I just need More RAM and More Power, as Tim the Toolman Taylor would say? More power is, of course, always the answer. But is it the only answer in this case? Or is there anything else to try?

Hi Forum! "Struggles" is a big understatement. I have a document with several hundred image files probably averaging a few megabytes each (total overall of a couple gigabytes). During the beta, I tried it first with "embedded" and then with "linked," but of course back then the "linked" feature didn't actually function, so it made no difference. After opening the document, it would take an hour to load it up, queuing everything into RAM/virtual memory somehow, I guess, and then it would be usable, though not perfect. At some point the "linked" feature did begin working, and so I rebuilt my entire document with links, and that caused the document size to go down dramatically. It did not really have the behavior that I would have hoped, however, as all the linked documents still appear to be forced to load upon opening the document. It just was semi-sort-of-usable during the process, and also my impression is that it took longer. I would have rather had only the images actually appearing on the screen to load. Then, upon scrolling to a new page, bringing a new image into active view, only then it would load the full image. It does appear that my vision was also the vision of at least part of the developer team, because if I break the links by renaming the image directory all the images show as a very low-res placeholder, and the document works great and I can edit it. If only this vision had been fully implemented! As it is, breaking the image links is the only way to work on the document without extreme, extreme pain -- one minute.. or multi-minute... delays... sometimes for every.... single..... mouse......... click. As the months have gone by (yes, long term project), the performance has gotten worse. It now really bogs down the whole computer. (Not Responding) is its typical state. Also it does crash hard sometimes. I see in the FAQ that everyone knows about scrolling around crashing it, but also sometimes in Resource Manager, or just... whenever. The most disturbing crashes are the times when I come back to the computer after it having sat overnight and the whole computer is totally unresponsive, the screen just stays black, and computer shut down is the only solution. Also the file size has ballooned (now at 143 MB), I'm not sure why, as I haven't been adding more nor larger images, just rearranging things and making changes. Perhaps the total file history is being saved to an extent, despite not having that checkmarked and creating new files constantly with "Save As"? This is not a problem, I don't really care, unless it is related to the other problems. Maybe helps you diagnose. I have tried messing with the performance parameters. Currently I have set: RAM Usage Limit: 5120 MB (The computer has 8 GB total physical RAM. Experimented quite a bit with this and this is where it seems to work best.) Disk Usage Warning At: 45056 MB (This seems to make absolutely no difference to anything. Placebo? Placeholder? Anyway, my HD has 65 GB free currently. Happy to free more if it would make any difference.) Undo Limit: 121 View Quality: Nearest Neighbor (lower quality) File recovery interval: 610 seconds Retina Rendering: Lowest Quality (fastest) Is there anything that will help me escape the torment in which I am trapped? Even a drop of water to cool my tongue, I would so appreciate. I see that version 1.8.0 may help stop the large complex document crashes, and so maybe it improves dealing with large documents overall, so I am going to try that now (I'm currently on 1.7.3). I decided to post this first so that the full saga can be followed, and any other poor large-document souls might find it and know: you are not alone.

Turns out it was not disabled, just changed. No longer activated through double-click, but through single-click, and has new shiny graphical elements. The change just happened to break image frames created under the old system, or at least ones that are on master pages. A new image frame created will function normally.

Likely you are aware, but if not: in the latest beta, 293, double-clicking on an image no longer activates the interface allowing scaling and rotating of the image within the picture frame. Using Windows 10. A feature thought in this area: it would be very great, and for many projects crucial, to be able to both get and change this information (exact scaling and rotation angle) in a dialog box.