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

Pšenda

Members
  • Posts

    8,883
  • Joined

  • Last visited

Everything posted by Pšenda

  1. From the beginning of the numerous occurrences of corruption and data loss, it is evident that the proposed architecture of files and working with them is not optimal (perhaps fast, but definitely not safe and definitely not efficient in terms of file size). Therefore, I personally assumed that the V2 version would bring some major change in the file format, because the frequency of negative experiences and the declared incompatibility with V1 directly encouraged it. Unfortunately nothing.
  2. Wouldn't it be appropriate to make one more common category in the FAQ, where general problems common to all versions would be placed? Now some FAQs are placed only under the V1 version (where the user with V2 does not have to look for them), but they are also valid for V2.
  3. The context between the UI and the type of installation is not mentioned by anyone here except you - so please do not confuse the user unnecessarily. The installation type is listed here in response to the issue listed here, which is obvious to everyone from the context of the posts and their continuity.
  4. Until the errors with saving and corrupting files are removed, the application should explicitly inform/warn the user about this when saving to an external/network/cloud drive. The information provided here on the forum "officially our developers recommend loading/saving files should be done to a local disk" is of no use to these users who have just lost their valuable data.
  5. Do you have images without a white background? (for example after using the Erase White Paper filter). Then you can just layer them on top of each other - the black outline of the character is still black, and the red areas will intensify. Heat map.afphoto
  6. And isn't "My Account" more appropriate? Personally, I find the mere designation "Account" without specification (My Account, Affinity Account, ...) a little strange.
  7. https://affinity.help/designer2/English.lproj/pages/GetStarted/zoom.html
  8. As far as I could notice, no one is trying to "discredit" the request stated here. The request has been made, and it is up to Serif (no matter what anyone writes here) when and if they will implement it at all. Since the implementation of the request will obviously take some time (there are far more important and for most users more beneficial requests that have been waiting for many years), so for the OP or other users of this discussion forum with a similar problem, an alternative to using Person in APublisher, with which you can easily switch the work environment and modify the layout of the panels, was presented here. And it is only up to the OPs/users if they will somehow use this information, or if they will put up with the existing application options while waiting for the implementation of the said request. P.S. I think even for such a high value professional user this discussion was useful - you're welcome
  9. If you open a file from ADesigner in APublisher, after switching to the Designer persona, the Artboard Tool is available (as in ADesigner), with which artboards can be created and added as well.
  10. I got the impression from your posts that you use all elements in your work, not just purely drawing, not just purely photo, not just purely text - for which, of course, work in specific applications is easier. However, if you use text and pixel tools in ADesigner, I think it is more convenient to use APublisher (because it can do almost everything that ADesigner does), and switch to the appropriate Persona as needed.
  11. Did he notice what I responded to? I think your reaction is completely out of line - because what you write was not discussed at all in Paul's post. File extensions were "only" talked about!
  12. Yes - that's why it's also not the subject of my request. But I assume you understood correctly that I (because I set up my OS and the assignment of the APublisher application to all affinity extensions) if I run APublisher with a *.afdesign file, since it is obvious (see the extension type) that I will most likely work in Designer persona so that this persona is automatically selected for me.
  13. It is clear that you did not understand my request at all - please try to read it.
  14. Have you tried it? I don't see anything that APublisher/Designer persona should have a problem with (except Export persona of course).
  15. I use APublisher precisely for the StudioLink function as the default application - so I also open *.afdesign and *.afphoto files in it. That's why I wrote this easy-to-implement requirement (https://forum.affinity.serif.com/index.php?/topic/168870-personas-changing-according-to-the-extension-of-the-file-being-launchedopened/)
  16. For these purposes, I use Personas in APublisher, because each persona can have its own specific settings of panels and tools. So when I draw - I switch to the Designer persona, and I have all the appropriate/necessary panels available. When I need to work with text, I switch to Publisher persona, where I already have prepared Character/Paragraph/Text styles panels, which of course I don't need when drawing.
  17. Thanks for the explanation. But that doesn't correspond at all to my panel display needs, so I wouldn't use this feature on the desktop. But for the needs of a small iPad display (and thus a very small workspace) it can be handy.
  18. However, it is shown there as well this too, which I don't know if and how it is related to the problem. Edit: Despite the fact, that the highlighted (blue) curves are different in the two images! vs
  19. I don't use the iPad version, so I don't know exactly how this "automatic" function works, but how does the application know that it should "automatically" collapse the panel because I no longer need it?
  20. The current implementation is definitely only "unfinished". Shrinking the preview according to the bounding box makes no sense (except perhaps for a simplified implementation*), because the bounding box has no meaning in the preview - it is not visible, it cannot be manipulated, so there is no reason to consider him in the preview at all. *) This may be decisive from the point of view of rendering speed.
  21. https://www.google.com/search?q=Affinity+for+Android+site:forum.affinity.serif.com
×
×
  • 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.