DanielL

@ dev team - I have filed a few bug reports already in the last couple of days, but I am seeing almost non-stop crashes with publisher on Windows 10. I can only work about 15 minutes maximum before I crash for any number of things. the last time I was simply trying to move the cursor left in the text block, or rotate an image. In addition, the entire setup is getting pretty sluggish. Clearly there is something else at play in the background, but hoping you might be able to review my file and or give me a beta version that has extensive logging enabled to help understand what is going wrong. I am so frustrated at this point that I need some help to figure out how to make this all work more reliably. Can you please reach out to me to help me figure out how to get past these issue?

I certainly do get full display on the local PC, I figured out how to finally get non-chrome based remote desktop to work which is preferred anyways as I can leave the laptop display closed when working remotely.

Found the setting now, thanks for the tip on how to get this the way I need it to behave. Cleared up a lot of preflight issues now 🙂

I am not sure if this is related to this spell checking thread or something different, if different feel free to move it to a unique thread as applicable. This is using the current 1014 beta version. I have three instances of the same word(callsign), only difference is the capitalization and punctuation I need the all caps to be learned as it is a control value and needs to be spelled as-is so I tell it to learn this word (right click on the one in blue). Both versions of the all caps are now accepted versions This leaves the lowercase situation which is a genuine spelling error and needs to be fixed, I expect to be able to right click it and fix the spelling. However the only option available is to "UnLearn Spelling" If its a learned spelling, why is it saying its spelled wrong still? If capitalization is important (and thus unique), it should instead give me the option to fix the spelling. This behavior feels inconsistant to me. okay, so I want to unlearn this capitalized spelling issue, so I go ahead and select the option to "Unlearn Spelling", I would expect the all caps to return to being spelled wrong, but that is actually the opposite of what happens here , all versions are now accepted as being spelled correctly. Continuing down the chain here, I try to use the undo feature to back out the learning. I can undo the learning for the all caps versions, but not the lower-case version of the word. I am now stuck with the wrong spelling being learned as lower case, and the right spelling in all caps being unlearned. This behavior is perplexing to me, seems like the spelling routines need some more work

I am working on a technical manual that cites programming language code. As you can imagine, the spell checker is going crazy trying to deal with the programming code chunks. In my current efforts I am using TCL which requires prepending a $ in front of variables so every variable is being flagged as a spelling error. Is it possible to add support for loading code blocks that would be ignored for spelling entirely, or add some other option like a formatting flag to ignore spelling. This would save my preflight from being a nightmare of spelling issues to wade through.

I have installed all apps on my main windows 10 laptop and trying to use my chromebook to connect to the laptop to work remotely with the lite weight chromebook. I have video and etc under teamviewer so I know that is all working as expected, but when I launch affinity publisher, I get the initial loading screen and then a blank white screen that I can't do anything with at all. It won't render or anything useful so it seems like something is failing to load properly when using a remote display rather than the local display. I am open to tinkering, let me know if you have any ideas on how to make this work on the remote machine.

I am seeing the publisher silently crashing quite frequently. I have the UI set to automatically send the crash reports. I see these crashes 5-6 times a day. I am a new user so not doing anything crazy yet, just manually migrating content from a MS word document. My document is about 160 pages currently, with say 35 of so (might be less) fairly low resolution images (place holders only so about 60 dpi each) and a few designer embedment's. other than that is just a huge amount of text so far. I can share my document, but would prefer to keep it private at this time, thankfully I only lose a small amount of work each time due to the frequent backups, but still super annoying being I have just bought all products and seeing this level of issue within 48 hours of my purchase... I added the 2 crash files I could locate, maybe the are autocleared?? I expected to find a lot more of these files 508fba78-9fd6-452a-94df-24350446d33c.dmp d41e3e8f-f3ed-4c91-a4a7-323f4fb71d6a.dmp