Jump to content

MikeTO

Members
  • Posts

    570
  • Joined

  • Last visited

Everything posted by MikeTO

  1. There's a thread in the Windows Photo Beta forum that also has Mac hardware benchmarks for Affinity. Check out my post from September 11 in this thread where I've compiled the benchmarks that others have shared.
  2. If I understand you correctly, you're clicking on an image that is used more than once in the document. The Resource Manager groups all instances of that image together with a caret to the left of the group. If the group is expanded, the Resource Manager should highlight the specific instance of the image and all should be well. But if the group is collapsed, clicking an image highlights the group and not the specific instance of the image. Expanding the group now won't help, the group will remain highlighted. To force the Resource Manager to highlight the instance you would now need to deselect the image on the page and click it again while the group is still expanded. Is this the issue you're talking about?
  3. The original request in this thread was to offer keyboard shortcuts for Place and Replace Image which already exist. There are also UI buttons for this - Place is in Tools and Replace Image is in the Context Bar. I agree that it would make sense to add Replace Image to the context menu but it's already so long. I use the keyboard shortcut for Replace Image constantly.
  4. Someday when scripting support is added, this would be an easy feature for one of us to create with a script.
  5. Ensure you choose Inline and not Float to keep the pinned image inside the text frame
  6. It depends on how you setup your new Mac. I did a restore from iCloud backup when upgrading from my old Intel MacBook Pro to my new M1 MacBook Pro and it worked like a charm. It was just like getting a new iPhone, minimal effort. I keep all of my work backed up to an external drive and I manually verified that the restore worked properly, which it did, but that's when you realize that not everything is backed up to iCloud so it can't all be restored. It was just some miscellaneous stuff that I had to copy over manually. I don't remember it all but for example, I rely on the Downloads folder in my MacBook's dock and that is device specific, it's not the same as the iCloud Downloads folder. I just had to copy those files manually. You'll have to deregister some apps and media on your old machine of course. For example, if you use iTunes then you'll have to deregister the device.
  7. Fair point. Fortunately, the most common Typography options are available from the Character panel. We all have our UI wishes, mine is Frame Properties which isn't a panel, a dialog, or a window, but a Context toolbar popup. At least you can keep Typography open if you want to and can position it anywhere on the screen. I work on a laptop screen so Frame Properties always overlaps the image I'm working on.
  8. The problem is the Left Indent setting for the TOC style - you can see it in the picture of the text ruler, that page number is aligned to the left indent setting. Change left indent to 0 and you should be fine.
  9. No, I'm using just my MacBook Pro's built-in screen. I'll be sure to give you a crash report next time. After the first few crashes I did do a lot of testing trying to replicate it. Even though I inserted the same index mark in the same way I was unable to replicate it so I wondered if the crash was related to something I had done prior to inserting the index mark and that the insertion of it was just the final trigger. The crashes were with the simplest form of index marker - just indexing something like Smith without a parent topic or style override. The only additional piece of data I can provide is that I keep Show Index Marks on so the app does have to draw the marker icon.
  10. FWIW, I have also experienced crashes when inserting an index mark. For me it has been very rare and I've never been able to reproduce it after restarting so I haven't previously reported it since I wasn't sure that it was specifically related to the index mark insertion or to something I had done just prior to inserting the mark. I've experienced it about half a dozen times out of the several hundred index marks I've inserted over the past year but it's frequent enough that I pause to consider whether I've saved recently enough before inserting a mark. I've also never been able to figure out why the insert Index Marker dialog sometimes sets focus to the Topic field upon opening and other times to the Parent Topic field. I've tried duplicating this, quitting Publisher between attempts and repeating the steps as identically as I can, and almost always focus is given to Topic but occasionally focus will be given to Parent Topic. There's something wrong with the initialization of this dialog and I haven't seen an issue like this in any other Affinity dialog. I doubt fixing this will fix the crash but who knows and it should be fixed anyway.
  11. I've reported this issue before but we determined it's a bug in macOS. I resisted that diagnosis at first since I hadn't seen the bug in other apps but I was later able to reproduce it in Apple's own apps. I've spent a great deal of time debugging this issue and I can now reproduce it on demand in any app that uses Apple's spell checker. I just tried it in Notes and Text Edit and triggered the bug in both apps within a minute. I've reported the bug to Apple but I don't think this one is going to get much attention unless a lot of people complain about it. There are three major symptoms of this macOS bug: Words are correctly underlined but not available to Guess/Learn/Ignore - this is very common but it's easy to workaround. Keep right clicking the word repeatedly until the options appear in the context menu. If they don't appear after a good number of clicks try right clicking another word and then return to the first until they appear. There's a second workaround if you get frustrated - copy the sentence to another app such as Apple Notes. After the word is flagged there right click it and Learn or Ignore the word from there. Words are incorrectly underlined (the word is already in the dictionary) - the workaround is to ignore it, the problem will resolve itself and eventually the underline will go away. It might take a long time. Words are not underlined so you don't even know they're not in the dictionary until days, weeks, or months later when they get underlined - there is no workaround for this one. However, if you want to be sure your document is fully spell checked one option is to copy the contents into another app such as Pages, Notes, or Text Edit and spell check it there. Although it's the same underlying spell check code, Affinity will process your copy in a different manner than Apple's own apps so you'll possibly find some more misspelled words. I just copied 150K words from Affinity to Apple Text Edit and found 5 more misspelled words by doing this. However be cautious, this won't find every misspelled word. I've verified that if you throw hundreds of misspelled words at both Affinity and and Apple app at the same time that neither will find all of them and there may be a few words that neither will immediately find. I'm thinking of reinstalling MS Office just for spell checking since it doesn't use Apple's buggy spell checker. There's one more bug with this feature that doesn't impact Affinity since it uses only the spell checking half of the macOS spelling and grammar checker - you can't turn off grammar checking in Apple's own apps including Pages, Text Edit, and Notes. They will flag potential grammatical issues even when Check Grammar is unchecked which is incredibly frustrating since the grammar checker has a very high false positive rate.
  12. No, it definitely controls the default language for an Affinity document. I can't say I fully understand what Affinity is doing though. For example. Set Preferences > General > Language to German, it will restart. Create a new document and draw a frame - Character > Language > Spelling will be German (you might have to factory reset your defaults). This works as I'd expect it to if the Language preferences is supposed to control the default language for a new document as it appears to do. Set Preferences > General > Language to English (which means United States), it will restart. Create a new document but don't draw a new frame yet - Character > Language > Spelling will be English (Canada) for me. I can't figure out why it is choosing Canada now. Yes, my macOS is set to English Canada but a second ago it took German from Preferences so why is it now taking English Canada from macOS? Factory resetting my defaults won't fix this. Now choose the Frame Text tool - Character > Language > Spelling will still be English (Canada) for me. Change it to English (which means United States). Choose Edit > Defaults > Save. Quit and restart Publisher just to prove it's not a session issue and create a new document but don't draw a new frame yet - Character > Language > Spelling will still be English (Canada) for me! Now choose the Frame Text tool - Character > Language > Spelling will change to English (which means United States). Choose the Move tool again - Character > Language > Spelling will be English (Canada) for me. This makes no sense. Anyway, draw a text frame and yes the language will be English (which means United States). So it sort of works fine. It doesn't matter whether I'm fiddling with English US or English UK, I get the same results. It's buggy but it's a system that works perfectly for American and British users which is why nobody pays attention to it.
  13. I believe this is because Edit Text Styles is a modal dialog and must be opened in the centre of the screen while Edit Brush is modeless and opens at the last-used position for user convenience.
  14. You're not doing anything incorrectly and it's definitely a design flaw. I've reported this before. This works much better for Americans than Canadians. Old Bruce is right, it's a flaw. Preferences > General > Language just offers English UK and English US but not English Canada or the other variations. It's a great design choice and probably worked well in 1.0 when I assume there were just UK and US English languages supported. But then more English variations were added without adding more UK variations so the design no longer works. Preferences > General > Language > Default will use the OS default. If you're in the UK it will default to English (which means UK) and if you're in the US it will default to English United States. This controls the UI language and the default language for new documents. Preferences > Auto Correct, Abbreviations, Title Exceptions, or Filler Text will all default to the correct language. Whether you set Language to Default or English (UK) or English United States, it will just work. You are lucky. First, here's the Preferences > General > Language list - note that "English" means UK English, it's just not named clearly. English (United States) means exactly what it says. Now let's look at Auto Correct or the other three Preferences panes. If Language = English, these other panes will default to English (United Kingdom) and if Language = English (United States) these panes will default to English (which means US). These lists were designed the opposite of Language with UK spelled out and US omitted. This is somewhat confusing but UK and US users probably never notice it because the system works as designed for them. But if you're outside the US or UK and have Preferences > General > Language set to Default or your specific English variation such as English (Canada), these panes will default to English (United Kingdom) and every single time you must manually select your language or you'll be editing the wrong version and will be confused when the data you edit does nothing. This is made worse because only English UK and US have default values for things like Auto Correct - these features really don't work for English users outside the UK and US unless you spend hours manually updating the features to duplicate what is included for UK and US users. UK vs. US vs. Canada/Australia... Consider a brand new non-UK/US English user who opens Affinity and although they had English Canada in macOS system preferences, Affinity defaults to English (UK). They go to Preferences and won't find an English Canada option so they have to come to this online forum and be instructed to use Edit > Defaults > Save to change their default language for new documents. While that feature makes sense, they really should be able to set their default language in Preferences and Affinity really should use the system default instead of giving them UK English. And while it's not important, it really would be nice if words like Capitalise were spelled correctly in the UI. The easiest way for Serif to fix this would be to create more UI language packages so the other English variations can be added to the Preferences > General > Language list. Affinity would simply work as designed without any other coding changes. It means more UI language packages which means more work as the menus and dialogs are modified. The alternative way to fix this if Serif really wants to keep the number of English UI packages to two is to: If Preferences > General > Language = Default and no default document language has been saved by the user, set the default document language to the system language which presumably would be English Canada or whatever. Default the Preferences > Auto Correct and other panes to the default document language rather than the UI language
  15. I cannot duplicate this tabbing behaviour on macOS - I can tab between Find and Replace all day and it never gives focus to the document. I must press Return/Enter. I wish Esc would cancel and shift focus to the document since there's no way to do that without using the mouse. I believe that Return/Enter must change focus to the document because Find/Replace is a panel and not a dialog. In every other panel with a text box you can press Return to complete the action and return focus to the document so it must work this way for consistency. It might be nice if Affinity offered both a panel and a dialog for the two main user patterns of finding/replacing, just like Office 365 does. But if I had to choose between a panel and a dialog I'd opt for what Affinity has now. It is very compact and lets me work on each result before clicking on the next one. My only real beef with Find/Replace other than the lack of Esc which I really don't care about is the issue of stale results. Search for something with multiple results. Delete the found text for the first one. Click the second one to view it. Now click the first one again - Affinity won't go back to that page because there is no text on that page that matches the find query - this is a stale result. Affinity should remove a result from the list when it no longer exists. In the meantime, those who really want to clear the search results can do so by typing something like qq and pressing Return/Enter. It's not a great shortcut but it's better than nothing.
  16. I just tested it and for me it worked as I described. Here's a screenshot showing the four scenarios, a frame from a master layer with filler text and another with normal text, and a frame from non-master layer with filler text and another with normal text. Affinity spell checked just the normal text regardless of whether it was in a master or non-master frame.
  17. Creating a calendar is a pretty niche use case so it's not surprising that apps like InDesign, Affinity, and Xara don't have it built in although Xara had it in their legacy app just like Serif. AFAIK Deneb doesn't have this feature and PageStream definitely didn't have it but it would have been trivial for somebody to write a script for PageStream to create a calendar wizard. There is a very full-featured calendar script wizard available from a third party for InDesign. Someday when Affinity offers scripting it would be easy to create a calendar wizard. I might write a script to draw stylized calendars because it would be straightforward and a fun project. But then once you've done that somebody will want holidays and you'll spend a lot of time finding a source of international holiday data. And then somebody will want you to add support for the 13-month Coptic calendar and the next thing you know it will no longer be a fun little project and will be real work. I think I've already talked myself out of it. 🙂
  18. It is one use case, but not the only one. For example, I type my chapter names directly into master page frames and I definitely want those spell checked. I also have a master that will have two variations of an image on the left and right pages and they need 'current' and 'original' titles above them. I type that text directly into a master frame. Serif can't turn off all spell checking on master pages just because one use case is to type placeholder text, there's no way for Affinity to know what is placeholder and what is real. Filler text is intended for assisting with the layout while avoiding spell checking - Affinity never spell checks filler text even if you've overridden the default filler text with your own through Preferences > Filler Text. You can certainly type your own placeholder text into master frames - I do it too, but you'll just have to avoid spelling errors. Or since you said you plan to replace this text you can simply ignore the preflight warning - what difference does it make if it's placeholder text that you will replace later? The same is true for images and I don't think Serif should turn off the preflight warning for image resolution on master page images. I have several "Placed image DPI too low" warnings all because I drew picture frames on maser pages and filled them with a grey placeholder image with FPO in the middle of them. The images are stretched too large so I get preflight warnings. I just ignore those because I'll eventually replace the images with the right ones.
  19. Instead of saving as package, try embedding all the images (Resource Manager, select all, Embed) and then linking them (just click Make Linked while they're all still selected). Then save.
  20. I trust iCloud because I understand exactly what it's doing and I know it's limitations. You and I are both old timers and we could compare our data loss scars but I really think you should try iCloud even if just for fun. The worst that can happen is that iCloud will stop syncing - today that will happen only because of a super large file but perhaps there will be some new bug in the future. But even if it stops syncing you will still be opening and saving your files locally until you notice and fix the problem because that's the way iCloud works, it saves locally first and then syncs to the cloud. The only ways I can think of to lose your files with iCloud are: Have a sync problem and then you replace your Mac and do a restore from iCloud without realizing that iCloud wasn't fully up to date. But you and I wouldn't do this, we'd always have an external backup and would ensure iCloud was up to date before doing a restore. Have a sync problem and then edit an outdated iCloud file with another device, or directly from the cloud in a browser. I never edit files from a web browser and I rarely edit with a second device. But if I do I always check that the file I'm about to open is the right version. It's different than Microsoft's cloud where the worst that can happen is really as bad as you can imagine - Office 365 can open the cloud version when the local version is newer or it can open the local version when the cloud version is newer, and then you'll lose the previously-saved changes. That won't happen with iCloud. The problem with iCloud is that people rely on it as their backup. It's great that they have it as a backup if they lose their device because hardly anybody backs up their files, but it's not a complete replacement for backing up your data. Using iCloud Drive is quite cool - it's great to be able to open a file on your iPhone when away from your Mac. And setting up a new Mac from iCloud is so much easier than the old fashioned way. IMO the worst thing about iCloud is the other services that sync through it. With iCloud Drive syncing, you can see exactly what has synced and delete it directly from the cloud if you want, you're in control. But with app service synching, the data is in a hidden database. For example, with Safari syncing of open tabs and frequently visited sites, if the data gets corrupted (which it can) there's no way for you to purge it and start over.
  21. That's correct, if I disable my network connection Affinity will be none the wiser, I will still be able to open and save all of my iCloud files. The changes will be synced when my network connection is restored. That's just the way iCloud works. Apps only know the iCloud path and when attempting to open an iCloud file macOS checks for a local copy in the user's Library folder and opens that if it exists. Only if there isn't a local copy does the app actually load the data from the cloud. Every one of my documents and images I have in iCloud is also on my local drive but this isn't true for a default setup. If you buy a new Mac and restore from iCloud your documents and images won't be downloaded to your Library folder until they're needed. I forced a full download to avoid issues with Affinity. I also never modify my Affinity files on another device so they're never outdated. If you modify data on another device then it's possible that the iCloud version will be newer than what's on your Mac. MacOS should sync the new data automatically but I can imagine there could be latency issues if you tried to open a document that used an image that hadn't synced yet. iCloud is far from perfect but this basic part of it works flawlessly. The biggest issue with iCloud is the bug with syncing getting stuck if you create too large of file which happened to me again while fixing the corrupted previews we're talking about. If you delete the big file immediately you'll be fine but if you don't notice it right away iCloud can get stuck and then you'll have to fix it manually. The approach Apple takes is to have you turn off iCloud syncing, delete all of your local files, and then restore from iCloud. This obviously makes me nervous so I backed up all of my local files to an external drive before doing it and after the restore was complete I went through every folder looking for lost files and I found several that hadn't been synced to iCloud after it got stuck. This took several hours so it's better to just delete huge files as quickly as possible.
  22. I should have kept a copy of the file for testing but I can't re-test now. Yes, the document and its images are saved to iCloud and I'm aware of that type of issue but I don't think that's what's going on. The cloud/NAS issue is due to the inherent latency of loading resources from an external location but in my case everything is also stored on the internal SSD and that's where Affinity is loading them from. Affinity can't load them from iCloud if they're stored locally. There are a couple of scenarios were you could run into trouble with iCloud. First, combining a local network with cloud syncing can lead to issues. I've been burned so many times using Office 365 with Microsoft Azure on a corporate network with unreliable wifi. That combination makes it easy to wind up with a newer copy in Azure than you have locally. But another scenario even for a single user without a network is multiple devices. If the images are updated by device A and you open the document on device B, then the images in iCloud might be newer than those stored locally if they haven't synced down yet which could lead to latency in opening the document's images. With iCloud, files are saved locally first and then asynchronously synced to the cloud. It's possible for the sync to iCloud to fail or stall but you'll always have a local copy, at least until you or the OS chooses to offload it. None of my files are offloaded so Affinity is opening the local copy, not the cloud copy.
  23. I think I've resolved this problem but it still makes me nervous so I thought I'd post about it. Publisher stores a preview of each linked photo for use in the thumbnails as well as to immediately render a photo before loading the externally linked photo. I've been working on a big book in Publisher for a long time and today the image previews became corrupted and I don't know how to resolve it. The thumbnails appear correctly except for the photos - the four images shown in this Pages panel thumbnail are nothing like the images - it's just garbage data. Notably, my file is usually 7MB when compressed and I'm not impacted by the file bloat problem but it wouldn't go below 17MB with this issue. So there was an extra 10MB of garbage data. When you go to a page, whether by double clicking it in the Pages panel or simply scrolling, Publisher shows the stored preview first and then replaces it with a higher resolution version. This became very noticeable to me because it first showed these garbage data previews in the main window and then replaced them with the actual photos. It's all very quick and it didn't impact printing or exporting but it's disconcerting and made me wonder whether I should abandon my current document and revert to a previous version. I restarted Publisher and restarted my Mac to no avail. Looking at the photos in the Resource Manager showed the same problem. I tried embedding and then relinking all of the photos but that didn't solve the problem. If I deleted a photo and added it back it was fine but given that I have hundreds of photos I was loathe to do that. I finally found a solution - I renamed the folder containing the images and allowed Publisher to relink them when I opened the file. With the photos linked, this resulted in a 2.5GB file due to the file bloat problem. But I embedded and relinked all the photos with the Resource Manager which got it back to 7MB. Anyway, it's fixed now but I was a bit worried about the document. I have a backup from yesterday but I'm glad not to have lost all of today's work. I'm using 1.10.5 with the latest macOS on an M1 Pro.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.