Jump to content
You must now use your email address to sign in [click for more info] ×

R C-R

Members
  • Posts

    26,430
  • Joined

Everything posted by R C-R

  1. I think a great many users resort to looking for documentation only for things they can't figure out far more quickly by doing a little experimentation once the app is installed. Besides, as you said, the documentation for the Affinity apps is far from complete or comprehensive. IOW, "learn by doing" is far more common than starting off via "RTFM" & typically even more effective for most things. As for what would need to be a very long list of features set to install by default, I seriously doubt the vast majority of users, pro or not, would want to waste any time scrolling through it looking for items to exclude. And no matter how it was presented, it would mean adding & maintaining more code to make sure all the necessary dependencies were included, not just for the initial install but also for updates that added new features, fixed bugs, & so on. It is in no way a "win-win" situation either for Serif or most users. Regarding support nightmares, I don't think you understand what I meant. Both Serif & users would need to know what any particular user had omitted from the install & if it had any relevance to whatever issue or question they wanted help with. So among other things, not all Window users know how to or even want to delve into the Registry, download & run some script or whatever to upload what they might consider in part to be personal or private info, or do anything else that would make what could already be complicated issues even more time consuming to resolve.
  2. I think users who frequently use this toggle would be annoyed if they had to dismiss a message or even had to set an option not to display it. Besides, if tapping this keyboard shortcut by accident needs a message to explain what it did, what about the dozens of other shortcuts that users might also tap by accident?
  3. To begin with, I think most users consider at least some of the various features in all the personas of AP very useful & well worth including -- even if they use some other app to develop RAW files, the Develop Persona offers various adjustments that can be applied to any RGB pixel layer. Likewise, the Liquify & Tone Mapping personas offer various ways to extensively modify the appearance of those layers, including Tone Mapping presets like the ones James Ritson created and any that users have created for themselves. So while you personally may not have any use for any of those features, I think most users would at least prefer to have them available without having to re-run an installer (which they may have to download again to use!). And of course, if you personally never use any of them other than the Photo persona you can always customize the toolbar to remove the Personas item. I also am not sure what you mean about wasting the resources to maintain the other personas. Users do not have to maintain them but Serif certainly does need to do that whether or not you use them because some if not most users do use them. Besides, if Serif did add the ability not to install them, they would have to add additional code & resources to the installers which would increase the amount of maintenance they would need to perform as new features were added, bugs fixed, etc. The same applies to the minimal security aspect because they would need to add more code to the installer to support those options. I also disagree with your comment that the apps are targeted specifically at experts, & beyond that, that even most experts (however you want to define them) would know enough to decide at install time which features they would want to use as they become more familiar with what the apps (& their updates!) are capable of doing. For that matter, the installer itself would have to include built-in pre-install help of some kind to guide new users through what could be dozens & dozens of install options, or at least a bunch of built-in links to online resources that explain what they are & any interdependencies they may have with other features, resources, etc. On top of all that, it make it a nightmare for both Serif & other users to offer or get support for the apps because nobody could be certain what anybody else had or had not installed or if that had any relevance to whatever issue they were asking about unless/until that was made clear to all involved. If nothing else, it would make it very tedious & time consuming to install & use the apps to their fullest & most useful capabilities, something I think most users & potential users would find of very little benefit & not worth the hassle.
  4. The same question applies for "parts / features" that are not initially installed. Would the user have to re-run the installer (after possibly having to download it again) to install any new parts / features they later decided they want or need? I'm not even sure that Serif could sell the apps in the Mac app store if all the options @lphilpot wants for the installer were available, & possibly the same for the Windows store version.
  5. For the Affinity apps, what exactly do you think are the parts / features the installer should ask users if they want included in the installation? Consider for example the multiplicity of tools for the Tools panels, all the various Studio panels, all the presets, & so on, plus all the *.dylib/frameworks & resource files that support various functions & features, & the various help files that explain how things work. I cannot image that very many user would want to have to wade through a huge list of such things, many of which they may not even understand what they are for before using the app, just to install any of the apps. The same consideration would apply to filetype associations, which users can change now at the per user OS level anyway.
  6. No, software developers do not, nor can they, change the default file binding (a.k.a. default app association) or in any way "override" the binding the OS sets for which app the filetype opens by default. That's just the way it is & always has been for ~30 years or so, which is why no app developer can 'fix' this -- it is something they have absolutely no control over if, when, or how the OS does this. They are on the list because Affinity Publisher V2 can open these filetypes, so removing them from the list would mean users who did not own Affinity Photo could not open them directly from the File > Open menu. This is something users have asked for since the early days of V1 & many are happy that it is now possible without workarounds. It's the same for RAW files -- as has been mentioned, they can be developed in APub; you just don't get the control over how they are developed like you do in AP. If it really bothers you that much, you could try making a feature request but you would have to do that not just for the Affinities but also for every other app that offers a list of file types it can open to the OS. Good luck with that.
  7. If you just click, it will launch the app so the trick is to click & hold.
  8. It will work from the Dock if you click & hold on its Dock icon until you get a popup menu & then hold down Control while choosing to open it from the popup.
  9. In APub V2 I never get a Develop progress bar for any RAW file. I have about 25 total *.cr2 files on my Mac. After checking them more carefully I realized most are not actually RAW files -- they are leftover files of a different filetype from DAZ 3D or an old version of Poser that Finders Kind incorrectly identifies as Canon CR2 raw Image files. That explains the unsupported error I was getting. However, the 3 that really are Canon *.cr2 files all open in Apub, all show an image via Quicklook, & all open in Preview.app. But never is their a progress bar, just a 'loading 1 document' notice in the main toolbar.
  10. Interesting. All I can tell you is on my Mac running Catalina Affinity Publisher 2 shows an 'unsupported' error for every CR2 file I tried it with. On your Mac, does it open as a developed pixel layer or something else? Like I said, the *.nef files I tried open via File > Open, but they also open via right-click choices in Finder. The CR2 files I tried will open pre-developed via the right-click but produce an error if I try to open them from the File menu. I do not have a lot of sample files of either type to test with buy time permitting I will try with some others.
  11. I assume you mean starting the app with the Control key held down. It is the same for all OS versions (both Mac & Windows).
  12. Probably so but it should not matter if Save is done from the File menu or via its keyboard shortcut.
  13. "has to"? – Do I understand right that you request the Affinity installer to influence/set/change your system preferences in macOS? I'm wondering if Apple's security rules would allow this or, if so, whether you really want to give Affinity the right to change your system settings. I think what @General Disarray meant is Serif should remove the filetypes from the Affinity Publisher info.plist file that Affinity Publisher cannot open, like certain RAW file formats. As it is, using File > Open in APub V2 will offer to open several file types not supported by APub (they are not greyed out) but if one is selected, the 'filetype not supported' error pops up. It's kinda weird though: some RAW file formats can be opened directly in APub V2, but they apparently are developed using some default setting so what you get is a pixel layer in the Publisher Persona with no control over the development settings. So for instance I can open *.nef test files I have on my Mac but not *.CR2 ones.
  14. FWIW, since it is evident the OP is using a Mac (note the 3 'traffic light' window buttons), unless the OP has changed the defaults, CTRL + S will not do anything.
  15. I for one would absolutely hate having to run through a long list of file types to be included in the Info.plist before I could install any of the Affinity (or any other) app!
  16. AFAIK, it is the OS, not the apps, that sometimes does this, typically when a new app is installed that signals to the OS that it can open open specific file types. IOW, the app does not force the OS to change the default binding of a file type to a particular app; the OS just assumes that because the app is newly installed the user wants that done.
  17. If you mean about 'activating' decimals, I think what @thomaso meant was to set Decimal Places for Unit Types for Pixels values to more than 1 decimal place, like to at least 3 or higher.
  18. Yes, it is CMD on Macs. This is a standard feature of most Mac apps, like when you want to select only certain files in Finder windows.
  19. The main thing to check is the startup time after you have restarted your Mac.
  20. It seems to vary, user to user. Personally, for me they seem to work about the same: All of them crash occasionally, but not often, & usually just when I am verifying that a bug someone has reported does in fact crash the app.
  21. Assuming the online version is meant, I'm not sure on my Mac it is doing more than showing the preview thumbnails, & like you said it doesn't do vectors (& many *.afpub) files very well.
  22. A bit clumsy but another way to do this without adding strokes or separating curves: Convert the letter to curves. With the Node Tool select the inside nodes of just the upper part of the B. In the Node Tool context toolbar select Transform Mode & then Selection Box from Curves. In the Transform panel, make sure the W & H proportion is locked (chain icon not broken) & for example in the W: field enter w*0.8 or w/1.5 or whatever you like to reduce the size of that inner B part. Repeat steps 2 through 4 with just the lower inside nodes of the B selected. This gives you separate control of how much each inner part is thickened if you want to do that, to use ruler guides to align edges if desired, & all the nodes remains editable without extra work.
  23. Technically, even if you do not have the same versions, or even if you do not have any version of Affinity Photo or Affinity Designer installed at all, by default* you will still see the other two persona buttons in Affinity Publisher. But if you click either of them you will get a StudioLink message telling you you must purchase the other apps to use those personas. (If they are installed but not yet updated to the same version, you can just open them separately, update them to the same version as Affinity Publisher, run them once, & then the buttons will work.) * Note also that in Affinity Publisher via View > Customize Toolbar... it is possible to customize the Toolbar, to remove the 3 persona buttons if you want.
  24. At least on my Mac running Catalina in Finder the names do not include the minor version numbers, so instead of open /Applications/Affinity\ Photo\ 2.4.0.app the command would be open /Applications/Affinity\ Photo\ 2.app. A simple way to see what is required is to open a Terminal window, type the word "open" followed by a space, & then from the Finder Applications window drag the app into the Terminal window. You can press return to open the app.
×
×
  • Create New...

Important Information

Terms of Use | 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.