Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by fde101

  1. There is a comment from a Serif employee somewhere on the forums that he was basically sitting right next to the people working on the DAM. It is happening, whatever it turns out to be, but no word on how long it might take. Guessing it might be a while.
  2. The situation is the same with Photo on the desktop and I believe this is intentional.
  3. The desktop versions can't do this yet either and people have been begging for it for a long time. Evidently Serif considers this something that will take significant time to implement and they are focused on other features for now.
  4. The desktop versions can't do this yet either and people have been begging for it for a long time. Evidently Serif considers this something that will take significant time to implement and they are focused on other features for now.
  5. Neither one - it is a limitation of the way that the file format is implemented. The Affinity programs do not keep the entire document cached in memory but rely on accessing data randomly from the saved document file. If the document file changes from underneath one of the Affinity programs or if the file becomes inaccessible, then the program can no longer reliably access the data in the file and does not have the information necessary to save it somewhere else, so it has no choice but to discard the document and no way to save it. This was recently explained in another thread.
  6. The definition of L*a*b* that I am finding is that L* is lightness (0 to 100), a* runs from green (-100%) to red (+100%), and b* runs from blue (-100%) to yellow (+100%). Neutral gray is found at a* = b* = 0. In that case, a fully desaturated image should be possible by ensuring that nothing contributes to a* or b* (leaving both at zero), and letting L* contribute to itself at 100%. A partially desaturated image would be a partial contribution of a* and b* to themselves at similar levels, assuming that it is a simple saturation reduction. I am basing this on the assumption that whatever part of max value is selected for a contribution is multiplied by the incoming value (ex. 50% => 0.5 * source value) and added to the other values to produce the final result. If the original value of b* was 100% (yellow), then a 50% contribution should give 50% yellow. If it was 100% blue, then a 50% contribution should be 0.5 * -100% => -50%, giving 50% blue. What am I still missing in how I am interpreting this?
  7. Just to help with diagnosing this: are you using separated mode by any chance?
  8. The Android equivalent of Metal would probably be Vulkan: https://developer.android.com/ndk/guides/graphics
  9. There are already other threads discussing this scattered across the forum. An SDK for native Affinity plugins is rumored to be in the works. No idea what kind of time table or what capabilities will be accessible using this SDK, but at least it sounds like it is coming... eventually...
  10. fde101

    Adding Text

    There are currently three programs in the Affinity suite - Photo, Designer and Publisher. You are asking about Photo, but you posted this in a section of the forum that is intended for discussing Designer. A moderator might move this to the appropriate place when they take notice. That said, this particular feature works the same way in all three applications in the Affinity suite.
  11. Serif does not normally respond to feature requests. Sometimes, but not usually. They do read them.
  12. If you are trying to replace all of them, and the symbols are not detached, you can always design the replacement separately, expand the symbol "container" in the layers panel, make sure Sync is turned on, drag in the new stuff, and delete the old stuff.
  13. Yeah, the price of QXP is rather high... consider though that the single-app price for InDesign is $21/month. You can get the three-year QXP advantage plan right now since 2019 just came out, using the competitive upgrade from a product you already have (PagePlus qualifies and can still be purchased for @25), for $750. That includes all major version upgrades within those three years. The single-app price for an InDesign subscription is $20.99/month, which works out to $755.64... so over a 3-year period it is about the same, except that QXP is a perpetual license, so if you stop paying, you keep the version you have, while with InDesign, you lose it. Oh, that and the upgrade prices after you have a QXP license are lower... so pushing it past 3 years the price advantage QXP has over InDesign increases.
  14. Yes, what @Hilltop outlined is the general method for setting a raster tile fill. Currently missing is the ability to create a vector tile fill. The existing feature doesn't work with SVG files, for example - only raster images. That is still missing.
  15. This could be done without an entirely new tool, as long as you are willing to settle for the limitations of only two colors, etc... we would simply need an "Apply Immediately" checkbox / toggle of some sort on the context toolbar.
  16. Serif does not normally respond to feature requests. Sometimes, but not usually. They do read them. https://en.wikipedia.org/wiki/Blend_modes#Divide It is apparently just what the name implies: take the corresponding pixel values of the two layers and divide one by the other.
  17. fde101

    Swaping characters

    the teh hte eth het eht
  18. NOTE: most of the below material was for Designer but in general Publisher works the same way... https://affinity.help/designer/en-US.lproj/index.html?page=pages/Layers/LayerMasks.html?title=Layer masking https://www.frankentoon.com/post/complex-masking-in-affinity-designer
  19. Bleed is not considered part of the intended content of the document, but is rather for the benefit of the printing process. Since the whole point of embedding a document is to show the content of one document inside of another, it kind of makes sense that the bleed would be hidden by default, since you would be positioning the document somewhere on the page and making the bleed visible in the document would in effect make something visible in the finished work that was not considered to be something that was intended to be seen.
  20. Unfortunately, this is normal behavior. It is not a bug, but it is annoying at times. I would suggest trying to arrange your panels in such a way that the change in size does not cause a significant impact to the way you work. This could stand to be improved.
  21. Subtract that component's contribution from the contribution coming from other channels?

Important Information

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.