Jump to content

- S -

Members
  • Content count

    539
  • Joined

  • Last visited

About - S -

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

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

  1. Image link: https://www.gettyimages.co.uk/detail/news-photo/ronnie-osullivan-of-england-reacts-during-the-quarter-final-news-photo/1136958522
  2. Not trying to force users to use *.tiff. Although seemingly trivial, it drives me nuts. See my post in the below thread: https://forum.affinity.serif.com/index.php?/topic/69667-photo-saves-as-both-tif-and-tiff/&do=findComment&comment=360869
  3. When placing an RTF file into a text frame using File > Place, the character styles for a second/third/etc. language don't set the language. The character styles themselves are imported, however they have no effect on the language set in Affinity Publisher. The language set in Affinity Publisher remains in the default language (EN-UK). Initially I was thinking that perhaps RTF doesn't support languages in styles, however the character styles seem to work OK in LibreOffice—so presumably they're supported, although I'm not sure about RTF support for using paragraph styles for language (as they don't work in either Publisher or LibreOffice). In the attached file 'Language Character Style.rtf': LibreOffice recognises the character styles and sets the language accordingly. Affinity Publisher recognises the character styles, however doesn't set the language accordingly. File: Language Character Style.rtf In the attached file 'Language Paragraph Style.rtf': both LibreOffice and Affinity Publisher recognise the paragraph style, but neither set the language accordingly (possibly a limitation of the RTF file format?). File: Language Paragraph Style.rtf ------ Windows 10 - 17763.379 (1809) Affinity Publisher - 1.7.0.257 (Beta) LibreOffice - 6.1.5.2 (x64)
  4. When placing an RTF file into a text frame using File > Place, paragraph styles where the style name begins with square brackets are lost. See below screenshots and attached test file. Test File: Brackets Paragraph Style.rtf ------ Windows 10 - 17763.379 (1809) Affinity Publisher - 1.7.0.257 (Beta) LibreOffice - 6.1.5.2 (x64)
  5. If you really want to get attention, tag the whole team in your sig, so that every time you post they get notified.
  6. I suspect you're using the 'Erase White Paper' filter on a black and white image? In which case, what you see on the screen isn't actually varying shades of grey (RGB), but varying alpha levels (A). If you're trying to use Levels and Curves on it, the Levels and Curves adjustment layers allow you to adjust the alpha channel by changing the drop-down from 'Master' to 'Alpha' (see below screenshots for layer layout, as the Levels/Curves adjustment layers need to be above the target layer rather than 'Child' layers; not sure why). You can also change the colour by using 'Colour Overlay' in Layer Effects (FX).
  7. It appears Microsoft have now updated the Microsoft Store revenue fees they mentioned at Build 2018 (better late than never I guess…): https://docs.microsoft.com/en-gb/legal/windows/agreements/app-developer-agreement-change-history https://docs.microsoft.com/en-gb/legal/windows/agreements/app-developer-agreement
  8. I previously posted about this HERE. Changing the display scaling to 125% on a desktop isn't a good solution as it makes everything too big. The jump between 100% display scaling and 125% display scaling is too big and setting a custom display scaling between 100% and 125% isn't officially supported. As there is no way to adjust the text size within the Affinity Software itself, I think it would be reasonable that Serif at least tries to accommodate for this Windows accessibility feature as best as possible. It would be unreasonable to expect you to support any size font, however perhaps you could test up to maybe 125% text scaling?
  9. Carry out the following steps: 1) Run the tool in the below link from the Microsoft website: https://support.microsoft.com/en-gb/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed 2) After running the tool to fix any issues, it should allow you to then uninstall the previous version of Affinity Publisher by going to [Windows Settings > Apps], and uninstalling Affinity Publisher. If it isn't listed as installed there, proceed to the next step anyway. 3) Once the older version of Affinity Publisher is completely uninstalled, run the installer file for the new version of Affinity Publisher (affinity-publisher-beta-1.7.0.249.exe). It should now install. 4) I suspect something (maybe file cleaning software; I don't know) has deleted files in C:\Windows\Installer. Files in this location shouldn't be deleted. If for some reason it fails to install again after doing the above steps (hopefully it won't), look in the %TEMP%\AffinitySetup\ folders for the two newest setup log files ('Setup.log' and 'SetupUI.log') and attach them to see why it's still failing.
  10. The error message the OP is seeing is a different issue. The error messages the user sees when access is blocked by 'Controlled Folder Access' are different. The Windows error would be "File not found. Check the filename and try again", and the Affinity error would be "Save failed because access to the file was lost." See my post HERE.
  11. - S -

    Searching

    A quick check here indicates that you’re correct about Google, but other search engines behave differently. You were right in your original post: there shouldn't be a space after the colon and this applies to not only Google, but also other search engines—including Startpage for example, who use Google results behind the scenes. With a space, it can also return results for other Serif subdomains, as well as non-Serif sites. Without a space, it only returns results for the specific forum.affinity.serif.com subdomain. Google without space: https://www.google.co.uk/search?&q=site%3Aforum.affinity.serif.com+exif Google with space: https://www.google.co.uk/search?&q=site%3A+forum.affinity.serif.com+exif Startpage without space: https://www.startpage.com/do/search?&query=site%3Aforum.affinity.serif.com+exif Startpage with space: https://www.startpage.com/do/search?&query=site%3A+forum.affinity.serif.com+exif
  12. In Windows (and I expect Mac as well) it’s possible to add multiple input languages via [Windows Settings > Time & Language > Language]; the user can then switch between languages on-the-fly either via the language selector icon on the Windows Taskbar, or by using the [Windows Key + Space bar] keyboard shortcut. When typing in other applications, they recognise the language the user has selected in Windows and will automatically set the text in the document to match that language. This means that the spell checking feature checks the spelling in the language that’s set and that the user is typing in. Affinity applications allow the user to manually change the language via the ‘Character’ panel, however it’s not possible to set it to change automatically. It would be useful if Affinity applications could recognise the language the user has selected in Windows and automatically change the text input language to match. This would mean the spell checking language would match the language the user is using to type, rather than basing it on the Affinity UI language in the Affinity preferences. Below are steps demonstrating what I mean in LibreOffice, Windows Mail, Affinity Photo and Affinity Publisher. Edit: I've since changed my mind about this. The problem with this method is if you go on to change the Paragraph Style afterwards, the language tags will be lost as the text gets set to the Paragraph Style language. So, while this method is quick and easy for say typing emails, for documents I think it's better to use Character Styles for the second language, and then manually apply that Character Style to any text in the second language; that way the language tags are kept when changing Paragraph Styles. The System Language toggle [Windows Key + Space bar] would then just be used to switch to the 'United States International keyboard' layout in order to use special characters—such as Grave Accent for example—that are missing from the standard UK keyboard. Language Steps.mp4
  13. - S -

    1.7.0.243 Issue / comments

    Up until around mid 2016, camera codecs were added to Windows 10 automatically by Microsoft via Windows Update, which meant Windows File Explorer would display Canon CR2 raw files natively without the user needing to do anything. For some reason Microsoft stopped updating the codecs around mid 2016 (I think Windows 10 (1607) was the last version that contained the latest camera codecs). Therefore, Windows File Explorer on Windows 10 machines will natively display raw files for cameras up to the Canon 80D (which was announced 2016 Quarter 2), but it won't display 5D Mk IV or later (which was announced 2016 Quarter 3). The 77D was announced in 2017 Quarter 1, therefore Windows File Explorer won't display thumbnails (or metadata) for it natively. Canon don't provide a codec to download either, which as you've found means at the moment you would need to install third-party codecs in order to see them in Windows File Explorer. However, for machines running Windows 10, Microsoft are going to add additional camera raw codecs to Windows 10 via an extension—where they can be updated independently from the OS. It's not available for the current general release version of Windows 10 (17763, 1809), however a beta version of the extension has been added to the Microsoft Store for Windows insiders running insider build 18323 or later. I'm not in the insider program therefore I don't know whether or not it's fully functional yet. Hopefully, it will be ready for the next Windows feature update (19H1), which should be released sometime in the first half of this year. Details of the beta extension for Windows insiders can be found here: https://www.microsoft.com/p/raw-image-extension/9nctdw2w1bh8
  14. It could be due to their Photoshop settings. Have the images that are opening in Adobe Camera Raw been processed with Adobe Camera Raw at some point before? I no longer have Photoshop installed to try, however I recall there used to be a setting in Adobe Bridge Camera Raw Preferences that would automatically open JPEG or TIFF images in Adobe Camera Raw if they had Adobe Camera Raw settings.
  15. With the Healing Brush tool selected: - If the 'Aligned' tick box in the top context tool bar is ticked, then the source will move with the brush. - If the 'Aligned' tick box in the top context tool bar is unticked, then the source will stay in the same location.
×